docs: add versioning and release-impact convention to CLAUDE.md - #99
Merged
Merged
Conversation
Codify that package versions are never bumped in PRs into main (handled separately on main via chore(release) commits), and that PRs touching a published package must state the expected major/minor/patch release impact.
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.
What & why
We bump published-package versions in dedicated
chore(release):commits onmain, not in feature PRs — but that wasn't written down, so reviewers (and agents) flag "no version bump" on PRs like #95. This records the convention and adds a PR-description requirement so release impact is signalled up front.Change
Adds a "Versioning and releases" section to the root
CLAUDE.md:main— versions for@neardefi/shade-agent-js,@neardefi/shade-agent-cli, and theshade-attestationcrate are bumped separately onmainviachore(release): <package>-vX.Y.Zcommits.Release impact
No release impact — docs/convention only, no published package touched.
🤖 Generated with Claude Code