Update devDependency verdaccio to v5.33.0 #1012
Closed
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.29.2
->5.33.0
Release Notes
verdaccio/verdaccio (verdaccio)
v5.33.0
Compare Source
ℹ️ℹ️ℹ️ℹ️ℹ️ℹ️
There will be no more updates for version 5.x. Please upgrade to version 6.x. Aside from requiring Node.js 18 as a minimum, there are no breaking changes.
ℹ️ℹ️ℹ️ℹ️ℹ️ℹ️
Bug Fixes
v5.32.2
Compare Source
5.32.2 (2024-09-12)
Bug Fixes
v5.32.1
Compare Source
5.32.1 (2024-08-02)
Bug Fixes
v5.32.0
Compare Source
Features
Bug Fixes
v5.31.1
Compare Source
5.31.1 (2024-06-06)
Bug Fixes
v5.31.0
Compare Source
(🗞️ hey (renovate/dependabot/other bots) 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
v5.30.3
Compare Source
5.30.3 (2024-04-06)
ℹ️ Verdaccio v6.0.0-beta.2 has been released, ready for user test to ensure the best backward compatibility, help us by trying it out.
Bug Fixes
v5.30.2
Compare Source
5.30.2 (2024-03-24)
ℹ️ Verdaccio v6.0.0-beta.2 has been released, ready for user test to ensure the best backward compatibility, help us by trying it out.
Bug Fixes
1ceb9f9
] https://github.com/verdaccio/verdaccio/pull/4560 (verdaccio/verdaccio@1ceb9f9)) (remove engine strict message in older Node.js versions)v5.30.1
Compare Source
5.30.1 (2024-03-24)
Bug Fixes
v5.30.0
Compare Source
🎉 3 new contributors
ℹ️ Verdaccio v6.0.0-beta.2 has been released, ready for user test to ensure the best backward compatibility, help us by trying it out.
Features
On the versions view there is a new filter that allows semantic versioning filtering (feedback is welcome)
Versions filter by semver range
Bug Fixes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.