This repository was archived by the owner on Jun 5, 2026. It is now read-only.
Publish stable releases from master to the latest dist-tag#68
Merged
Conversation
patocallaghan
changed the title
latest dist-tag
Put the staged-publish workflow into its real shippable state. A package that ships stable releases from master only needs one path: publish reviewed master code to the default `latest` dist-tag. The prerelease/`next` flow is an advanced, opt-in capability this package doesn't use, so it isn't baked into the reference. - `npm stage publish` runs with no `--tag`, so it defaults to `latest`. - The release-source guard refuses any release not reachable from master (the prerelease exemption is removed) and fails closed with a clear message if the master fetch fails. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
patocallaghan
force-pushed
the
patoc/publish-yml-shippable-dist-tag
branch
from
926f340 to
5259bc4
Compare
7nights
approved these changes
Jun 5, 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Why?
Put the staged-publish workflow into its real shippable state. A package that ships stable releases from
masteronly needs the one path: publish reviewed master code to the defaultlatestdist-tag. The prerelease/nextflow is an advanced, opt-in capability this package doesn't use, so it shouldn't be baked into the reference workflow.How?
npm stage publishnow runs with no--tag(defaults tolatest), and the release-source guard refuses any release not reachable frommaster(the prerelease exemption is removed, so the guard applies to every release).Generated with Claude Code