Fix npm release lockfile - #293
Merged
Merged
Conversation
jsturtevant
reviewed
Sep 2, 2026
jsturtevant
reviewed
Sep 2, 2026
jsturtevant
approved these changes
Sep 3, 2026
Signed-off-by: Ludvig Liljenberg <4257730+ludfjig@users.noreply.github.com>
ludfjig
force-pushed
the
fix/npm-release-lockfile
branch
from
September 3, 2026 18:27
4232408 to
b567c5d
Compare
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.
Fix the npm release dry run by keeping optional platform dependencies on the latest published version until the release workflow updates them.
#238 introduced
just set-versionbut it was never tested and didn't work (as can be seen when my pr was merged and prerelease job failed)