Fix the npm release: explicit latest tag and bin path#35
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem & Solution Overview
The
v1.3.0release published via OIDC (auth worked) butnpm publishwas rejected: an old2.0.0exists on the registry, so npm would not implicitly move thelatesttag onto the lower-but-newer1.3.0. The publish step now passes--tag latestexplicitly. Also normalizes thebinpath (./bin/servergen.js→bin/servergen.js) to match the form npm stores and silence a publish warning.Testing Done
release.ymlvalidated;binmatches the published1.2.0form. Re-taggingv1.3.0after merge re-runs smoke → publish.