Repository navigation
Keep npm latest current during beta - #4
Open
sammeltassen wants to merge 3 commits into
Open
sammeltassen wants to merge 3 commits into
sammeltassen wants to merge 3 commits into
Conversation
This branch has not been deployed
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.
Publishing a new beta updated npm's
betatag but leftlateston an older beta, so default installs selected the previous release. After each beta publication, advancelatestwhile it still points to a beta. Preserve stable defaults, avoid downgrading newer betas, and require the target to match npm's currently publishedbeta.Apply this policy in GitHub Actions and local publishing. The trusted publisher needs Allow npm dist-tag enabled independently of Allow npm publish; the workflow installs npm 11.21 or later for OIDC tag management. No extra manual workflow mode or package command is added. Correcting the existing tag once can use
npm dist-tag add @allmaps/slides@0.1.0-beta.2 latestfrom a logged-in terminal.Update the publishing-command test fixture to include the helper and mock both registry reads and npm writes. The tests also verify that a failed npm tag update prevents Git release tagging.
Validation: all 226 workspace unit tests passed locally; workflow YAML parsing and
git diff --checkpassed. Both GitHub checks passed on commit18ddbca: Slides architecture (including native alignment, development smoke and fresh-package builds) and Static renderer (container build and entrypoint). No live npm tags have been changed.