build: update all non-major dependencies #27625
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:
7.8.0
->7.9.0
7.8.0
->7.9.0
v4.1.4
->v4.1.5
v2.7.2
->v2.7.3
0.21.1
->0.21.2
0.21.1
->0.21.2
0.21.1
->0.21.2
0.21.1
->0.21.2
0.21.1
->0.21.2
9.2.20
->9.2.21
9.2.20
->9.2.21
23.0.158
->23.0.162
1.77.0
->1.77.1
1.77.0
->1.77.1
7.6.1
->7.6.2
7.6.1
->7.6.2
6.16.0
->6.16.1
6.16.0
->6.16.1
5.30.3
->5.31.0
Release Notes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v7.9.0
Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v7.9.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
actions/checkout (actions/checkout)
v4.1.5
Compare Source
What's Changed
user.email
to be41898282+github-actions[bot]@​users.noreply.github.com
by @cory-miller in https://github.com/actions/checkout/pull/1707Full Changelog: actions/checkout@v4.1.4...v4.1.5
aspect-build/bazel-lib (aspect_bazel_lib)
v2.7.3
Compare Source
Using Bzlmod with Bazel 6:
common --enable_bzlmod
in.bazelrc
.MODULE.bazel
file:Using WORKSPACE
Paste this snippet into your
WORKSPACE
file:What's Changed
Full Changelog: bazel-contrib/bazel-lib@v2.7.2...v2.7.3
evanw/esbuild (esbuild)
v0.21.2
Compare Source
Correct
this
in field and accessor decorators (#3761)This release changes the value of
this
in initializers for class field and accessor decorators from the module-levelthis
value to the appropriatethis
value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:Allow
es2023
as a target environment (#3762)TypeScript recently added
es2023
as a compilation target, so esbuild now supports this too. There is no difference between a target ofes2022
andes2023
as far as esbuild is concerned since the 2023 edition of JavaScript doesn't introduce any new syntax features.SBoudrias/Inquirer.js (inquirer)
v9.2.21
Compare Source
quicktype/quicktype (quicktype-core)
v23.0.162
Compare Source
v23.0.161
Compare Source
v23.0.160
Compare Source
v23.0.159
Compare Source
sass/dart-sass (sass)
v1.77.1
Compare Source
npm/node-semver (semver)
v7.6.2
Compare Source
Bug Fixes
6466ba9
#713 lru: use map.delete() directly (#713) (@negezor, @lukekarrys)nodejs/undici (undici)
v6.16.1
Compare Source
What's Changed
fire-and-forget.js
by @tsctx in https://github.com/nodejs/undici/pull/3229Full Changelog: nodejs/undici@v6.16.0...v6.16.1
verdaccio/verdaccio (verdaccio)
v5.31.0
Compare Source
(🗞️ hey renovate users, read this)
ℹ️ Important changes added to the
.verdaccio-db.json
and token signature for users that run on Node.js 22 or higher (in the future 🙃 ) please readhttps://verdaccio.org/docs/configuration/#.verdaccio-db
TLDR:
[VERWAR007] VerdaccioDeprecation: the secret length is too lon...
to remove it please read the link above.verdaccio-db.json
and the token inside does not complies with the length (read link above) the application startup will fail with fatal error (Error: Invalid storage secret key length, must be 32 characters long but is....
)In both cases by updating the secret all previously tokens will get invalid, in your benefit a new legacy signature will be applied and is more secure than the old one (generating tokens with salt).
For existing installations that have no issues by invalidating tokens is recommended to add to the
config.yaml
the following setup, this will automatically generate a new the secret once is started, could be removed aftewards, if all went succesfull the[VERWAR007]
deprecation will not be displayed anymore.Any new installation should not worry about this, new token signature and secret (32 characters) is applied by default.
Features
Bug Fixes
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.