Repository navigation
chore: pin ct-agents v0.2.0 and ct-conventions v0.7.1 - #478
Merged
Merged
Conversation
The recipes are read from a git-ignored clone at the pinned tag, not from main. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…s .ct-conventions and .ct-agents Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
ocots
changed the title
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.
Pins ct-agents v0.2.0 and ct-conventions v0.7.1 in
AGENTS.md(ct-agents#16, part 1). The recipes, the release among them, were read frommainof ct-agents: a change reached every package at once, and a report could not say which version of a procedure it had applied.The recipes are now read from a git-ignored clone in
.ct-agents/at the pinned tag (the clone command is inAGENTS.md, not a submodule, as for the conventions), the Recurring tasks section points to it, and the proposal of a release states the versions applied: ct-agents, ct-conventions, and the commit of the CTActions clone the release tool runs from.The clone of the conventions is renamed
.ct-conventions/(it was.conventions/) to match.ct-agents/:AGENTS.md(links, clone command),.gitignore,CONTRIBUTING.md, and_typos.toml(which also excludes.ct-agents/) follow. ct-conventions v0.7.1 changes the name only: no rule changes, so there is nothing to re-audit.On a machine that has the old clone:
mv .conventions .ct-conventions, or delete it and clone again with the command ofAGENTS.md.To bump a pin later: change the tag in
AGENTS.md(the "Pinned version" line and the clone command) and clone again; the commands, one per pin, are in ct-agentsrecipes/pin-conventions.md.Docs,
.gitignoreand_typos.tomlonly, no code and no workflow.🤖 Generated with Claude Code