* chore: bump chromium in DEPS to 76.0.3807.2
* chore: update patches
* fix: Don't leak system network context when nw service is disabled
https://chromium-review.googlesource.com/c/chromium/src/+/1632494
NetworkService is now deleted by using SequnceLocalStorageSlot
on the IO thread when the service is disabled, which expects
all associated NetworkContexts on that sequence to be destroyed.
* chore: bump chromium in DEPS to 76.0.3808.1
* fix: Destroy all network contexts before primary network context
* chore: update patches
* Simplify out-of-process service registration
https://chromium-review.googlesource.com/c/chromium/src/+/1615882
* [ThreadPool] Rename base::ThreadPool to base::ThreadPoolInstance
https://chromium-review.googlesource.com/c/chromium/src/+/1634851
* fix: -Winconsistent-missing-override warnings
* chore: bump chromium in DEPS to 76.0.3809.1
* chore: update patches
* Change CreateBrowserMainParts to return unique_ptrs
https://chromium-review.googlesource.com/c/chromium/src/+/1632532
* chore: bump chromium in DEPS to 76.0.3809.3
Fixes: #18503
Refs: https://chromium-review.googlesource.com/c/chromium/src/+/1576232
For whatever reason Chromium made this change and then made the default
//content behavior to return false for all IsDataResourceGzipped
requests. This PR updates our ContentClient impl to return the correct
values.
Notes: Fixed issues where some `chrome://*` URLs would not render
correctly
* fix: update the FileSelectHelper to support the new promise API
Fixes#18254
So it turns out we've successfully introduced a way to write
non-typesafe C++.
This fixes two things:
* Uses the object the promise resolves
* Ensures we attach the Then handler before moving the promise
* fix: also fix misuse of Promise::Then in the download manager
This adds a patch to support functionality that we were using but chromium changed it. Electron uses breakpad on windows, chromium uses crashpad (which is newer). So this patch is needed until we update electron to use crashpad for windows.
* fix: ensure the inspector agent is shutdown before cleaning up the node env
* spec: add tests to ensure clean shutdown with connected inspector agent
* Update node_debugger.cc
* build: ensure consistent package-lock across multiple machines
* build: fix linting errors and use npm ci instead of npm install
* build: use a yarn.lock and yarn instead of package-lock and npm
* chore: replace package-lock.json files with yarn.lock
* chore: replace last instance of `npm install`
