docs(sparkline): clarify CI-owned release flow in CLAUDE.md#4
Merged
Conversation
aba1adf to
777deec
Compare
777deec to
d443cf3
Compare
d443cf3 to
066f4e8
Compare
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.
Summary
The
## RulesGit line referenced a non-existentrelease.ymland told contributors topnpm version+ hand-edit the CHANGELOG. The reusable workflow (coroboros/ci@v0) actually pinspackage.jsonto the tag and rewritesCHANGELOG.mditself on every tag — local bumping conflicts with it.Change
Rewrite the Git rule surgically:
main-only, branch → PR → squash-merge → tag, and an explicit never bumppackage.json/CHANGELOG.mdlocally — CI owns both. Drops the stalerelease.ymlreference and thepnpm versioninstruction.Test plan