Repository navigation
docs: correct first npm dev publish tag guidance - #43
Merged
Merged
Conversation
|
Warning Review limit reached
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Next included review available in 56 minutes. View limit detailsLimit details: You’ve used all 2 included reviews currently available. Your 63 included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour. The included review limit has been reached and this organization has disabled usage-based review continuation. Wait for reviews to reset or ask a billing admin to change After included review limits. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
Comment |
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
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.
The first-publish runbook incorrectly warned that
npm publish --tag devmight createlatest. npm's dist-tag documentation says--tagoverrides that default and lists no first-publication exception. The runbook now states the expected tag state and requires checking it after bootstrap. The actual release decision is whether to make the immutable first package version publicly available through@devand its exact version.Sources: https://docs.npmjs.com/adding-dist-tags-to-packages/ and https://docs.npmjs.com/cli/v11/commands/npm-dist-tag/ . This changes operator guidance only; it does not publish the package or move a tag.
API and SDK contracts are unaffected. CLI runtime and workflow behavior are unaffected; the existing workflow already uses
--tag dev. Public docs remain unchanged because no package has shipped. Feature-release flags, audience, and availability remain unchanged; first publication still needs the npm owner's decision and credential.Validation: Prettier check for the edited runbook and
git diff --checkpassed. Hosted CI is the final repository gate.Need help on this PR? Tag
@codesmithwith what you need. Autofix is disabled.