WEBDEV-9025: Add a CLAUDE.md covering the publish flow - #94
Open
jbuckner wants to merge 2 commits into
Open
Conversation
The README's publishing section is written for the GitHub web UI, so it doesn't say what the pre-release checkbox actually does or give a terminal path. Write down the parts that only live in npm-publish.yml right now: - The release's prerelease flag is what picks the dist-tag, alpha vs latest. - package.json holds the version that gets published, not the tag name. - Publishing is OIDC trusted publishing with no token, so it only works from the workflow, and a manual publish is identifiable by its missing provenance attestation. - Finals come off main only, branches publish prereleases. Also covers the worktree and merge-not-rebase conventions, and points at the README for everything else. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DaEr5YT1xpjK5ydNZPvjwx
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #94 +/- ##
=======================================
Coverage 84.69% 84.69%
=======================================
Files 38 38
Lines 1274 1274
Branches 303 303
=======================================
Hits 1079 1079
Misses 115 115
Partials 80 80 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
…ixed QA ran the documented commands. pnpm version writes a bare-version commit message and a v-prefixed tag, so say where the prefix comes from. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DaEr5YT1xpjK5ydNZPvjwx
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
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.
The README's publishing section is written for the web UI ("Tap
Draft a new release") and doesn't say what the pre-release checkbox does, so this writes down the bits that only live innpm-publish.yml: the prerelease flag is what picks thealphavslatestdist-tag,package.jsonholds the version that actually gets published (not the tag name), and publishing is OIDC trusted publishing with no token so it can't be done from a laptop. Plus thegh release createcommands and the worktree/merge conventions.Everything in it was checked against the repo, the tags, the workflow run history and the npm registry.
Worth knowing separately:
0.2.12is npm's currentlatestbut has nov0.2.12tag, no GitHub release, and no provenance attestation, so it was published by hand. Recorded on the ticket, not fixed here.WEBDEV-9025: https://webarchive.jira.com/browse/WEBDEV-9025
🤖 Generated with Claude Code
https://claude.ai/code/session_01DaEr5YT1xpjK5ydNZPvjwx