chore(release): cut v1.8.26 - #434
Merged
Merged
Conversation
Bumps the seven canonical version surfaces plus CITATION.cff date-released (1.8.25 -> 1.8.26, 2026-08-27 -> 2026-09-05) and adds the CHANGELOG entry for the three units merged since v1.8.25: the pre-commit credential fail-open fix (#433), the workflow job-graph guard (#183), and the skill trigger-accuracy eval (#398). The release notes lead with the one thing an adopter must act on: re-run the INSTALL copy. .githooks/pre-commit is a copy the user made and deploy.sh never rewrites it, so the fix does not reach an already-installed hook on its own. Without that line the release would claim a fix most existing adopters do not have - the same over-promise class the release itself fixes. Downstream delta measured rather than described: of the 26 files changed since v1.8.25, 6 are in the deploy set. The three credential tools are core tier and force-update; the eval suite deliberately does not ship. No engine, gate order, deployed file set, or configuration change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
SSoT sequence 168->169 with the completion record at the top of Ship History; rotated at cap 10 (Ship-fix-agents-md-backlog-write-scope-178-2026-08-23 -> archive/ship-history-2026.md, 151 -> 152 entries, no duplicate, no relative links to re-depth). Work Log moved to archive/ with its date suffix and appended to the hash-chained INDEX.jsonl (prev_sha 3a792eb8); check_audit_chain.py reports the chain intact. The rotation target named in the first draft of the ship entry was wrong - it still said the #398 eval entry, which the previous rotation had already moved past. Corrected against the file before writing rather than published and fixed afterwards. validate.sh after these writes: pass=99 warn=4 fail=0 skip=3, exit 0. Co-Authored-By: Claude Opus 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
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.
Cuts v1.8.26. Seven canonical version surfaces plus
CITATION.cff date-releasedbumped, and a CHANGELOG entry for the three units merged since v1.8.25.What this release carries
repo-gotchas.md§16 shipstests/ci/onlyThe one thing an adopter must act on
.githooks/pre-commitis a copy the user made, anddeploy.shnever rewrites it. An unmodified.githooks/pre-commit.guard-ssot.sampleis updated for them and a modified one arrives as.acx-incoming, but until they re-run the INSTALL copy their active hook keeps the old fail-open dispatch. The release notes lead with that sentence. Without it the release would claim a fix most existing adopters do not have — the same over-promise class the release itself fixes. The mechanical remedy (a deploy-time[STALE HOOK]check) is filed as #197 and deliberately not attempted here.Downstream delta — measured, not described
git diff --name-only v1.8.25..HEADgives 26 files; intersected withdeploy_manifest_golden.txt, 6 reach an adopter: the four credential files,repo-gotchas.md(§16), andcurrent_state.md(scaffold tier — the adopter's own copy is preserved).run_skill_eval.pyandeval/skills.yamlare not in the deploy set. The three credential tools arecoretier and force-update, so the first-commit block closes for everyone automatically; the hook does not.Evidence
tests/ci/test_release_version_consistency.py— 2 passed after the bump (it derives the canonical version fromdeploy.shand requires all eight surfaces to agree, plus aCITATION.cffdate not older than the newest CHANGELOG release).test_deploy_tiering.py+test_pre_commit_hook.py→ 47 passed, 1 skipped. This is a subset, not CI-equivalent — the full 947-test suite runs on this PR's three Windows shards, which is the real environment for it. No local full-suite claim is made for this cut.1.8.25outsideCHANGELOG.mdandarchive/sits inside the v1.8.25 Ship History entry, whichship.mdforbids editing.Not done
#195(the two credential screens' detection surfaces differ — needs a spec decision, not a patch),#196(credential_floor.ps1ships with zero runtime callers),#197(no stale-installed-hook detection), and backlog#194's remaining downstream-audit scenarios, which stay unaudited, not clean. All are named in the release notes rather than left implicit.Post-merge this still needs the lightweight
v1.8.26tag andgh release create --latest— that step is not complete at merge and this repo has forgotten it twice.🤖 Generated with Claude Code