Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency verdaccio to v5.31.0 #6578

Merged
merged 1 commit into from May 13, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 13, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
verdaccio (source) 5.30.3 -> 5.31.0 age adoption passing confidence

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 read
https://verdaccio.org/docs/configuration/#.verdaccio-db

TLDR:

  • Enforced for users that runs verdaccio via npmjs, for all Docker image isuers, verdaccio uses Node.js LTS 21 and the secret migration is voluntary until next major release.
  • For Node.js 21 or lower a new deprecation will appear [VERWAR007] VerdaccioDeprecation: the secret length is too lon... to remove it please read the link above
  • For Node.js 22 if you have already a storage with .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.

security:
  api:
    migrateToSecureLegacySignature: true

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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested a review from a team as a code owner May 13, 2024 00:13
@renovate renovate bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels May 13, 2024
@renovate renovate bot enabled auto-merge (squash) May 13, 2024 00:13
Copy link

πŸ“Š Benchmark results

Comparing with 9214bc4

  • Dependency count: 1,347 (no change)
  • Package size: 312 MB (no change)
  • Number of ts-expect-error directives: 993 (no change)

@renovate renovate bot merged commit f13209b into main May 13, 2024
48 checks passed
@renovate renovate bot deleted the renovate/verdaccio-5.x branch May 13, 2024 00:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants