Repository navigation
Prepare the 1.3.0 advisory release - #1129
Merged
Merged
Conversation
- Version 1.3.0 in pyproject.toml and __version__, the plugin and marketplace manifests, .well-known, the in-tree runtime lines, the capability-lock example, the determinism boundary and llms-full.txt. - CHANGELOG: Unreleased promoted to "1.3.0 - 2026-11-07", one line per change, with the application regression and the Q2 line stated plainly; the full prose moves to docs/changelog/1.3.0.md. Every PR merged since v1.2.0 is cited: #962, #987, #995, #1088 and #1123/#1124 gained citations, and the CI- and lock-only PRs share one line. - STABILITY.md: title, intro paragraphs and 22 migration notes stamped 1.3.0. - Schemas: generated, then pinned (15 documents new since 1.2.0). The host-grants 0.9 inventory and baseline documents no longer say "0.9 has not shipped in a tagged release", which the tag would freeze false. - .github/release-channels.json declares 1.3.0 advisory.
…lines The codex boundary-result goldens pin tool.version, which the full suite enumerated after the bump. The release note's opening says "several ways", not "most of it", and the control-completion line names the MCP input it means.
Brings in #1127 (the #1075 trust-root fix), which 1.3.0 must carry. CHANGELOG.md conflicted because this branch promoted the Unreleased section #1127 added a line to; both files are regenerated from main's Unreleased by the same cut script, so #1127's entry is a one-liner in "Verification, attestation and control", joins the verify highlight, and its full prose is in docs/changelog/1.3.0.md. Its STABILITY migration note is stamped 1.3.0, and llms-full.txt rebuilds identical.
The development corpus ran on 04fc9ce (this preparation with #1127): 39 partial, 6 not_established and 4 timeouts; no added, removed or changed row; 415 not_established candidates. All 49 answers equal those of main at 952a74c, which the release record's regression figures come from. Q0 37/49 (retained), Q1 0/49, Q2 0/49, down from 4/49 and 3/49 at the 2026-10-05 ledger. run.py exited 1 on the four timeouts; that is recorded, not a blocker. The holdout has no pinned members. The ledger test now accepts a null answer_id for a member whose row says it has no answer (timeout, refused, unavailable), never with Q1: the first ledger with timeouts. The release record links the ledger, and the release heading is dated 2026-11-08, the day the cut was finalised.
pengfei-threemoonslab
added a commit
that referenced
this pull request
Nov 8, 2026
main promoted `## Unreleased` to `## 1.3.0 - 2026-11-08` and stamped the migration notes 1.3.0 (#1129). #1128 is not in the prepared 1.3.0 notes, so its CHANGELOG entry moves to a new `## Unreleased` section, and its STABILITY migration note, still `Unreleased`, moves above the 1.3.0 notes. Both texts are unchanged; everything else is main's.
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.
Prepares v1.3.0 on the advisory channel, from
main, perdocs/release-runbook.md§ Cutting the release, steps 1–3, and § The advisory release channel, step 1. The owner approved shipping 1.3.0 frommainby 2026-11-15, with the application regression stated plainly in the notes. Nothing here merges, dispatches, tags or publishes.What changes
pyproject.toml,__version__, the Claude Code and Codex plugin manifests, the marketplace entry and.well-known'sversion.docs/agent-contract-current.md,llms.txt,docs/ai-search-summary.md, and the pilot ledger's source-tree label, which discloses that its cells were not re-measured), the capability-lockv0.9example and the determinism boundary.llms-full.txtis regenerated byscripts/build-llms-full.py.LATEST_PUBLISHED_VERSION,release_status.latest_release, the Action and pre-commit pins, the bundled prompts) stay at1.2.0until step 8, after publication.## Unreleasedbecomes## 1.3.0 - 2026-11-08: an introduction, the application regression, the migration summary, highlights and one line per change, about 12 KB.docs/changelog/1.3.0.md, grouped as in the release note. A script checked that every prose line arrived, and that the older sections are byte-identical.v1.2.0is cited. fix(openshell): preserve expansions and bind selected policy links #962, fix(privacy): withhold bearer tokens and curl user passwords in published values #987, Move the pre-commit example rev to v1.2.0 and guard it (#796) #995, build(deps): refresh dev, build-backend and publish locks; uv 0.13.1, pydantic 2.14.1 #1088 and feat(capability): record tool definitions in the capability lock and publish capability_payload/v2 (#1117) #1123/feat(attest): record who approved the change from host-supplied reviews (#1118) #1124 gained citations. The CI-, test- and lock-only PRs share one "No runtime change" line: docs(benchmark): measure current application review usefulness #961, test(ci): measure the 13 unmeasured test files so shards balance #979, ci: split the suite into five shards #996, fix: support PEP 508 extras-qualified pins in dependency lock verification #1007, fix: preserve distribution identity for extras-qualified lock pins #1009, Build(deps): Bump actions/download-artifact from 8.0.1 to 8.0.2 in the github-actions group across 1 directory #1013, test(ci): keep fixture scans out of the runner's step summary and outputs #1101, docs(changelog): backfill Unreleased entries for merged PRs without one #1111, test(static-only): key the allowlist by enclosing function, not line number (#1078) #1113. build(deps): bump hatchling 1.32.4, rfc3161-client 1.0.9, msgpack 1.2.3, platformdirs 4.12.2 #966/build(deps): refresh all four locks with uv 0.13.6; hatchling 1.33.0, sigstore 4.5.1 #1107 (rfc3161-client1.0.9, GHSA-87gx-4x38-2j9q) and Build(deps): Bump actions/setup-python from 7.0.0 to 7.1.0 in the github-actions group #1095 (actions/setup-python7.1.0 in the Action) get Packaging lines.952a74cfeb:not_establishedcandidate, and no row is wrong.STABILITY.md. The title, five "Unreleased …" intro paragraphs and all 22## Migration Note: Unreleasedheadings now say 1.3.0.python scripts/generate_schemas.py, then--pin: 15 documents new since 1.2.0 are pinned, and no existing pin moved.0.9inventory and baseline documents said "Extended in place:0.9has not shipped in a tagged release" (three model docstrings inschemas/host_grants.py). The tag would freeze that sentence false, so it now reads "New in0.9.".github/release-channels.jsondeclares1.3.0advisory.Protected paths: owner review
.github/release-channels.json: the1.3.0: advisorydeclaration. A tagged version's entry can never change.pyproject.toml: the version only.scripts/published_schema_pins.jsongains 15 pins.docs/host-grants-{inventory,baseline}-schema.v0.9.jsonget description wording only, before their first publication.Deliberately left for step 8 (after publication)
llms.txtanddocs/ai-search-summary.mdstill call contract 42 "unreleased, ahead of the latest public release". That stays true untilv1.3.0is published, and step 8 moves those lines with the latest-release constants.diffquotes are held bytests/test_host_diff_entry_docs.pyto the newest published release. They are re-captured from the published 1.3.0.Owner steps after this PR
v1.3.0and push the tag.pypienvironment gate.#1127 and the Q2 ledger
main(b581c39) into this branch instead of rebasing, so no force-push was needed.CHANGELOG.mdwas the only conflict. Both changelog files were regenerated frommain's Unreleased section by the same cut script:verifyhighlight.benchmark/application-q2/results/2026-11-08-04fc9ced.mdwith its.scores.json. It ran on the development corpus with the release build, 04fc9ce. Every commit after it changes no source.partial, 6not_establishedand 4timeout.added,removedorchangedrow, and 415not_establishedcandidates.Q2: 0/49 development (3/49 at the 2026-10-05 ledger), holdout not yet pinned.main's at 952a74c, the run the regression figures quote.run.pyexited 1 on the four timeouts. That is recorded in the ledger and does not block the release.test_every_ledger_says_what_its_scores_saynow accepts anullanswer_idfor a member whose row shows it has no answer (timeout,refusedorunavailable), and only with Q1 false. This is the first ledger with timeouts. The benchmark README documents it.Verification
pytest -m "not perf" -n auto -rfEsran in a venv built fromconstraints/dev.txt(pydantic 2.14.3) plusconstraints/build-backend.txt(hatchling 1.33.0), against 8ec1c8d (before fix(trust): treat manifest-declared policy packs as trust roots (#1075) #1127). There were three failures:test_codex_check_boundary_json_golden_outputs: the codex boundary goldens pintool.version. Fixed in 8ec1c8d, and the test passes.test_check_answers_an_unmodelled_settings_key_in_every_format. They fail only on this machine, whose global git ignore hides.claude/settings.local.jsonfrom the fixture's commit. The test file is unchanged frommain.test_verify_pr_controlled_inputs, the schema freeze, the release channel, shard partition and the codex goldens. The ledger's three benchmark tests pass too. CI runs the full suite on the head.python scripts/generate_schemas.py --checkpasses under pydantic 2.14.3, with all 15 new documents pinned.1.3.0section is 12,152 characters, against the 125,000 limit. Every prose line of the old Unreleased section is indocs/changelog/1.3.0.md, and every section below1.2.0is byte-identical.🤖 Generated with Claude Code