Repository navigation
docs, ci: plan 2.1 on a release/2.1 branch - #281
Merged
Merged
Conversation
Lists the 2.1 steps in dependency order with their PRs: safety net (#270), data contracts (#277, then #268 + #276), engine (#266), terminal output (#271), and removing legacy/ last, with the judge flow (#267) in parallel. Each merges into main as it's ready; 2.1.0 is tagged once at the end, and v2.0.4 is the fallback. The Deferred entry for removing legacy/ now notes that v2.0.4 announced it and points to the plan. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
So main stays releasable, legacy scripts included, until 2.1 ships: the 2.1 steps target release/2.1, which merges into main once at the v2.1.0 tag; fixes, docs, and non-breaking changes keep going to main and are merged into release/2.1 regularly. ci.yml and live.yml now run for release/2.1 as well as main (pull requests into it and pushes to it). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Summary
Sets up how 2.1 is built: the steps accumulate on a
release/2.1branch, somainstays releasable, legacy scripts included, until 2.1 ships.docs/roadmap.md: new "Release 2.1 plan" sectionrelease/2.1, which merges intomainonce; that merge is taggedv2.1.0.main(test: guards that keep code changes from moving scores #270, feat: install averacommand that works from any folder #278, feat: let the user-side LLM write in another language #269), andmainis merged intorelease/2.1regularly.legacy/, last, as announced in v2.0.4legacy/now points to the plan.CI:
ci.ymlandlive.ymlalso run forrelease/2.1(pull requests into it, pushes to it), so the branch gets the same checks asmain, including the integration layer and live smoke test on merge.After merging
Create
release/2.1frommain, so it starts with the CI change.🤖 Generated with Claude Code