Repository navigation
docs: release order for a contract change - #68
Merged
Merged
Conversation
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.
Aligns CLAUDE.md with omartelo/lich#712 (docs/hooks/README.md, Versioning).
The old wording ("a contract change that lands in lich first") read as "release lich first" and blocked a correct plugin release. A lich release may fetch files only the new plugin release ships, so the order is: the contract merges in lich,
tests/lich-refpins that merge, the plugin release is tagged here, and the lich release that installs it is cut last. Older lich releases never pick up the new plugin, since their version ceiling stops below its minor.Docs only, no version bump.