fix(WasmPlayer): pass --tag latest to npm publish - #2014
Merged
Conversation
npm now refuses to guess a dist-tag for a prerelease-looking version and errors instead of publishing — every version here is beta (see root CLAUDE.md's Releasing section), so latest is the correct tag to use explicitly, not a workaround. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This was referenced Aug 9, 2026
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.
Summary
npm-publish.yml's `npm publish --access public` failed on the first real run (v6.0.0-beta.50, see run 31321215262) with:```
npm error You must specify a tag using --tag when publishing a prerelease version.
```
npm no longer guesses a dist-tag for a prerelease-looking version string. Every Quest Viva release is
X.Y.Z-beta.N(see rootCLAUDE.md's Releasing section — the project deliberately never leaves beta), so there's no separate "stable" line to protectlatestfrom —latestis the correct tag to pass explicitly here, every time.Test plan
npm publish --access public --tag latestreproduced locally against a real Release AppBundle build (dry-run pack succeeded with matching contents; the--tagflag itself just changes which dist-tag gets set, not the publish payload)