Fix package version in lock file on publish #1216
Merged
Conversation
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
After we publish a new version of the package, the `package-lock.json` file is always out-of-sync, containing the old version number of the package until `npm install` is run. Run `npm install` before the Git commit step so that the lock file is updated with the latest version.
tombruijn
added a commit
that referenced
this pull request
Aug 27, 2025
This should no longer be necessary in future releases thanks to #1216.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
After we publish a new version of the package, the
package-lock.jsonfile is always out-of-sync, containing the old version number of the package untilnpm installis run.Run
npm installbefore the Git commit step so that the lock file is updated with the latest version.[skip changeset]
[skip review]