chore(deps): update dependency verdaccio to v5.31.0 #6578
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.30.3
->5.31.0
Release Notes
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 - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
π¦ Automerge: Enabled.
β» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
π Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.