You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cut v2.2.0 of the apexyard framework. The dev branch has accumulated 17 PRs since v2.1.0 (2026-05-25) spanning local agent routing, split-portfolio v2 hardening, and release-cycle plumbing fixes. Time to ship them to main and tag.
Scope
Pick semver bump: 6 feat: + 10 fix: + 1 chore: since v2.1.0, no NEW breaking commits → MINOR → v2.2.0
Generate the ## [2.2.0] — 2026-05-29 CHANGELOG entry from the conventional-commit log
Open release PR release(#NNN): v2.2.0 from release/v2.2.0 → main
After merge: tag v2.2.0 on upstream/main, push tag
After tag: run /release-sync v2.2.0 (mandatory step 9 of the release flow)
Acceptance Criteria
CHANGELOG entry added at the top of CHANGELOG.md covering the 17 PRs grouped by Added / Fixed / Changed
Release PR opened against main from release/v2.2.0
Release PR body carries a <!-- multi-close: approved --> marker (release PRs legitimately close many tickets)
Rex code review passes
CEO /approve-merge recorded
After merge: v2.2.0 tag pushed to upstream
After tag: /release-sync v2.2.0 opens the main→dev sync PR (or confirms already in sync)
Risks / Dependencies
Risk: PR feat(#448): /release-sync carry forward CHANGELOG.md from main to dev #451's CHANGELOG carry-forward is brand new — first release where the path-specific step 5b in /release-sync will run for real. Tests passed in the sandbox; production behaviour gets validated by step 9 of this release. If the carry-forward misbehaves, the sync PR Rex review catches it before merge.
No external dependencies.
Glossary
Term
Definition
Release-cut model
apexyard's gitflow-lite: daily PRs merge to dev; main only receives release PRs from dev. AgDR-0007.
/release-sync
Mandatory follow-up skill that syncs main back to dev after every release, preventing squash-merge SHA divergence from accumulating.
MINOR bump
semver: backwards-compatible new functionality. Triggered by any feat: in the conventional-commit log when no breaking marker is present.
Driver
Cut v2.2.0 of the apexyard framework. The dev branch has accumulated 17 PRs since v2.1.0 (2026-05-25) spanning local agent routing, split-portfolio v2 hardening, and release-cycle plumbing fixes. Time to ship them to main and tag.
Scope
feat:+ 10fix:+ 1chore:since v2.1.0, no NEW breaking commits → MINOR →v2.2.0## [2.2.0] — 2026-05-29CHANGELOG entry from the conventional-commit logrelease(#NNN): v2.2.0fromrelease/v2.2.0→mainv2.2.0onupstream/main, push tag/release-sync v2.2.0(mandatory step 9 of the release flow)Acceptance Criteria
CHANGELOG.mdcovering the 17 PRs grouped by Added / Fixed / Changedmainfromrelease/v2.2.0<!-- multi-close: approved -->marker (release PRs legitimately close many tickets)/approve-mergerecordedv2.2.0tag pushed toupstream/release-sync v2.2.0opens the main→dev sync PR (or confirms already in sync)Risks / Dependencies
/release-syncwill run for real. Tests passed in the sandbox; production behaviour gets validated by step 9 of this release. If the carry-forward misbehaves, the sync PR Rex review catches it before merge.Glossary
dev;mainonly receives release PRs fromdev. AgDR-0007./release-syncmainback todevafter every release, preventing squash-merge SHA divergence from accumulating.feat:in the conventional-commit log when no breaking marker is present.