docs: defer new-package release steps to the npm-bootstrap-package skill#563
Merged
Conversation
- Shrink ‘Releasing a new package’ to the why, the skill pointer, and a short no-skill essence (build first, publish without --provenance, npm trust + mfa=publish); the skill is the canonical procedure - Replace the outdated npmjs.com web-UI Trusted Publisher walkthrough with the npm trust CLI equivalent - Start new packages at version 0.0.0 instead of 0.1.0: nx release bumps from the manifest, so 0.1.0 with breaking commits overshot to 0.2.0 Claude-Session: https://claude.ai/code/session_01PDZBfA1bj35oc7Yqn1pc2n
- Remove the npm-bootstrap-package skill paragraph: the repo is public and outside contributors do not have that skill (the pointer now lives in project memory); keep the skill-free essence and the pre-merge npm view check - Back the 0.0.0 starting version with the observed releases: 0.0.0 landed search-typesense and text-normalization at 0.1.0, while pipeline-shacl-sampler pre-set to 0.1.0 shipped 0.2.0 Claude-Session: https://claude.ai/code/session_01PDZBfA1bj35oc7Yqn1pc2n
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.
The ‘Releasing a new package’ section in AGENTS.md near-duplicated a private bootstrap runbook and had drifted from it: it still described the npmjs.com web-UI Trusted Publisher flow (superseded by the
npm trustCLI), and the new-package starting version had been flipped to0.1.0based on an assumption the release history contradicts.Changes
npm viewcheck, and the manual essence: build first,npm publish --access public --otpwithout--provenance, thennpm trust github … --allow-publish+npm access set mfa=publish. The web-UI Trusted Publisher walkthrough is replaced by the CLI commands.0.0.0, not0.1.0. The first CI release bumps from the manifest over the package’s full history (no tag yet), it does not publish the manifest version as-is. Observed:search-typesenseandtext-normalizationstarted at0.0.0and landed their first release at exactly0.1.0, whilepipeline-shacl-sampler, pre-set to0.1.0, shipped0.2.0as its first-ever version.https://claude.ai/code/session_01PDZBfA1bj35oc7Yqn1pc2n