5.31.0 (2024-05-11)
(đī¸ 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.jsonand 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: trueAny new installation should not worry about this, new token signature and secret (32 characters) is applied by default.