Repository navigation
docs: refresh CLAUDE.md - #46
Merged
Merged
Conversation
- Correct the npm-publish note: publishing is now automated via a trusted-publishing (OIDC) publish job in release.yml, replacing the stale claim that no CI step publishes and npm publish must be run locally.
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.
Corrects a stale note in
CLAUDE.mdabout how releases reach npm.The file stated that no CI step publishes to npm and that
npm publishmust be run locally after each release. The release workflow now publishes automatically: afterrelease-pleasecuts a release, apublishjob runs — gated onrelease-created— and pushes to npm via trusted publishing (OIDC, no stored registry token). The note now describes this automated flow and thepush-event guard that prevents a green-CI pull request from cutting a release.No other content changed.