highlight package freeze before deployment#2158
Merged
Conversation
swaldmann
approved these changes
Oct 23, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The tip is quite easy to overlook because it does not look like an actionable item. The
package-lock.jsonneeds to be updated if there already is one... which is not uncommon, so I think we should include it as a regular step.After a
cds add mtawe recommend to:So I'd suggest we also document it here instead of the
npm update. Thenpm updatealso changes all other versions which were not changed in thepackage.json.Of course it is important to regularly run
npm updateto use the latest versions.