Repository navigation
v5.7.0
Minor release — 2 features, 9 fixes, 1 improvement.
Behaviour change: /approve-merge now stops a merge when the PR is behind its base branch (#1406). The check is on by default. Set merge.require_up_to_date to false in .claude/project-config.json to turn it off.
Added (feat)
- (#1420) make reviews faster with a severity bar, delta re-reviews and CI-first testing — 020fbab
- (#1351) add opt-in ORBIT planning adapter — 6d8f24b
Fixed (fix)
- (#1419) block a merge when a merge gate cannot load a library — cdb57f1
- (#1406) stop a merge when the PR is behind its base, and make /release-sync keep main-only changes — c16860e
- (#1404) honor the active ticket for unparsed write targets, and document a reviewer test path — 9d46ee2
- (#1400) scope the active-reviewer marker per session and stop owner-name leak false blocks — 5c12554
- (#1397) cover .astro in the design gate, exempt Alembic env.py, and warn when config overrides drop defaults — d60a0d4
- (#1399) validate Mermaid in every diagram-producing skill and align the DFD template with threat-model — 5be9ecb
- (#1355) stop Claude Code always-loading rule bodies — 6870a8b
- (#1373) skip CodeQL analysis outside the upstream repository — c66d7c5
- (#1353) pass Orbit record root to validation — 7e561ec
Changed (refactor / chore / docs)
- (#1398) load the writing rule in every agent, add a no-search-MCP fallback, and make Rex verify acceptance criteria — 2b6ed42
Closes
- Closes #1350
- Closes #1354
- Closes #1370
- Closes #1376
- Closes #1385
- Closes #1386
- Closes #1390
- Closes #1396
Migration script
- The release needs a per-adopter note, but no file move.
.claude/migrations/v5.6.3-to-v5.7.0.shprints it and exits 0.docs/upgrading.mdhas a matching row.
Testing
The changelog range is 020fbab..upstream/dev from the v5.6.3 Released-From trailer. It has 18 commits and 12 changelog entries. The 6 other commits are release, sync, and merge commits, which the generator excludes by design.
bash .claude/migrations/v5.6.3-to-v5.7.0.sh: prints the note, exit 0.test_update_chain.sh: 0 failed.test_release_changelog.sh: all 91 tests passed.test_v54_migration.sh: PASS=6 FAIL=0.markdownlint-cli2onCHANGELOG.mdanddocs/upgrading.md: 0 issues.
After merge:
- Confirm the
auto-tag-on-release-pr-mergeworkflow creates tagv5.7.0onmain. - Confirm
git describe --tags --abbrev=0 upstream/mainreturnsv5.7.0. - Confirm the squash commit carries the trailer:
git log -1 --pretty=format:'%(trailers:key=Released-From,valueonly)' v5.7.0. - Run
/release-sync v5.7.0.
Refs #1421
Glossary
| Term | Definition |
|---|---|
| Squash merge | GitHub combines the PR's commits into one new commit on main. The new commit has a new SHA. |
| Auto-tag | The auto-tag-on-release-pr-merge.yml workflow. It tags the squash commit and creates the GitHub Release after a release/v* PR merges. |
| Behind-base check | The step in /approve-merge that stops a merge when the PR's head is behind its base branch (#1406). |
/release-sync |
The follow-up skill that merges main back into dev after a release, so the next release has no squash divergence. |
Released-From trailer |
A commit trailer with the dev SHA this release was cut from. The next release reads it to find its changelog range (AgDR-0094). |
🤖 Generated with Claude Code
https://claude.ai/code/session_01KGvb2ba4gyT3TN8L2uMLTn
Released-From: 020fbab