Repository navigation
docs: name template v1.9.0 in CLAUDE.md (#103) - #104
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.
Fixes #103.
Acceptance criterion (verbatim):
grep -n 'v1\.8\.0' CLAUDE.mdreturns nothing and the stated template version matchesref:in.rhiza/template.lock.What changed: the two stale references in CLAUDE.md's "What this repo owns" section — the synced template version and the workflow-stub ref — now say
v1.9.0, matchingref: v1.9.0in.rhiza/template.lockand the@v1.9.0stubs in.github/workflows/.Gates:
make fmt— all hooks passed.make test— 156 passed, 1 skipped, 100% coverage.Not addressed: the issue's aside about re-checking the release-workflow paragraph is outside the criterion; the SHA-pinning itself is #102's PR.
Closes #103