build: update all non-major dependencies #24402
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.7.2
->5.7.3
5.7.2
->5.7.3
5.46.0
->5.46.1
5.46.0
->5.46.1
5.7.2
->5.7.3
0.16.2
->0.16.4
0.16.2
->0.16.4
0.16.2
->0.16.4
0.16.2
->0.16.4
15.0.2
->15.0.3
8.4.19
->8.4.20
8.4.19
->8.4.20
1.56.1
->1.56.2
1.56.1
->1.56.2
Release Notes
bazelbuild/rules_nodejs
v5.7.3
Compare Source
Bug Fixes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v5.46.1
Compare Source
Note: Version bump only for package @typescript-eslint/eslint-plugin
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v5.46.1
Compare Source
Note: Version bump only for package @typescript-eslint/parser
evanw/esbuild
v0.16.4
Compare Source
Fix binary downloads from the
@esbuild/
scope for Deno (#2729)Version 0.16.0 of esbuild moved esbuild's binary executables into npm packages under the
@esbuild/
scope, which accidentally broke the binary downloader script for Deno. This release fixes this script so it should now be possible to use esbuild version 0.16.4+ with Deno.v0.16.3
Compare Source
Fix a hang with the JS API in certain cases (#2727)
A change that was made in version 0.15.13 accidentally introduced a case when using esbuild's JS API could cause the node process to fail to exit. The change broke esbuild's watchdog timer, which detects if the parent process no longer exists and then automatically exits esbuild. This hang happened when you ran node as a child process with the
stderr
stream set topipe
instead ofinherit
, in the child process you call esbuild's JS API and passincremental: true
but do not calldispose()
on the returnedrebuild
object, and then callprocess.exit()
. In that case the parent node process was still waiting for the esbuild process that was created by the child node process to exit. The change made in version 0.15.13 was trying to avoid using Go'ssync.WaitGroup
API incorrectly because the API is not thread-safe. Instead of doing this, I have now reverted that change and implemented a thread-safe version of thesync.WaitGroup
API for esbuild to use instead.ng-packagr/ng-packagr
v15.0.3
Compare Source
postcss/postcss
v8.4.20
Compare Source
@layer
.sass/dart-sass
v1.56.2
Compare Source
Embedded Sass
protocol.
Configuration
📅 Schedule: Branch creation - "after 10:00pm every weekday,before 4:00am every weekday,every weekend" in timezone America/Tijuana, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.