Repository navigation
ci: release workflows and ct-conventions v0.7.0 (model for the packages) - #623
Merged
Merged
Conversation
… recipe Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…uite, docs dispatchable ReleaseGate.yml and ReleaseTag.yml call CTActions' release-gate.yml and release-tag.yml. Breakage.yml calls breakage-suite.yml (one report, the REL1 check of a release PR) and also runs on push to main and by hand: the baseline of the next release PR. Documentation.yml accepts workflow_dispatch, which ReleaseTag uses on a new tag. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Breakage — packagesTested commit:
|
This was referenced Oct 19, 2026
Closed
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.
The model of the release setup for the packages, after control-toolbox/CTActions#104, #105 (merged) and #107, and the recipe control-toolbox/ct-agents#11 (merged) and #13.
AGENTS.md: ct-conventions pinned atv0.7.0,RELin the index of the rule files, the one merge exception (a release PR inautonomousmode, withrelease.jl mergeonly), and a Recurring tasks section pointing to the release recipe.ReleaseGate.yml(new): the gate of a release PR,REL1–REL7, on every PR; a PR that does not change the version passes at once. It also checksREL6on every PR (the registration bot mentioned in no PR text nor commit message).ReleaseTag.yml(new): on push tomaintouchingProject.toml, tags the merge commit of a release PR, creates its GitHub release and runs the documentation on the tag;GITHUB_TOKENonly.Breakage.yml: now callsbreakage-suite.yml(one report and one comment per run, instead of one comment rewrite per cell; theREL1check of a release PR against the run on the base), and also runs on push tomainand by hand, which gives the next release PR its baseline. Same six packages, same label.Documentation.yml: acceptsworkflow_dispatch(used byReleaseTag.ymlon a new tag, which triggers no push event).CHANGELOG.md: two lines under[Unreleased].No source change. No repository setting needed: the merge of a release PR is checked by
release.jl readyfrom what actually ran, not by required checks.Checks: the gate run locally on this branch → "not a release"; actionlint on the four workflows touched → clean, except a pre-existing finding on the tag filter of
Documentation.yml('v[0-9]+\.[0-9]+\.[0-9]+':\.is not a valid escape in GitHub's filter syntax), left as is since the docs did deploy on the tags v0.30.9–v0.30.11; markdownlint onAGENTS.mdandCHANGELOG.md→ 0 issues;.conventionsre-cloned atv0.7.0. The labelrun breakageis added to run the new suite for real, its first run.🤖 Generated with Claude Code