Skip to content

Prepare the 1.3.0 advisory release - #1129

Merged
pengfei-threemoonslab merged 4 commits into
mainfrom
claude/release-1.3.0-cut-prep
Nov 8, 2026
Merged

pengfei-threemoonslab merged 4 commits into
mainfrom
claude/release-1.3.0-cut-prep

Conversation

@pengfei-threemoonslab

@pengfei-threemoonslab pengfei-threemoonslab commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor

Prepares v1.3.0 on the advisory channel, from main, per docs/release-runbook.md § Cutting the release, steps 1–3, and § The advisory release channel, step 1. The owner approved shipping 1.3.0 from main by 2026-11-15, with the application regression stated plainly in the notes. Nothing here merges, dispatches, tags or publishes.

What changes

Protected paths: owner review

  • .github/release-channels.json: the 1.3.0: advisory declaration. A tagged version's entry can never change.
  • pyproject.toml: the version only.
  • Frozen schemas:
    • scripts/published_schema_pins.json gains 15 pins.
    • docs/host-grants-{inventory,baseline}-schema.v0.9.json get description wording only, before their first publication.

Deliberately left for step 8 (after publication)

  • llms.txt and docs/ai-search-summary.md still call contract 42 "unreleased, ahead of the latest public release". That stays true until v1.3.0 is published, and step 8 moves those lines with the latest-release constants.
  • The README and quickstart "not yet released" diff quotes are held by tests/test_host_diff_entry_docs.py to the newest published release. They are re-captured from the published 1.3.0.
  • The pilot ledger's dry run is re-measured on the published build.

Owner steps after this PR

  1. Merge this PR.
  2. On the merged commit, dispatch Release Engine Smoke (unqualified), then Advisory Release Rehearsal on the same commit. Re-running the smoke after the rehearsal changes the tagged manifest.
  3. Tag v1.3.0 and push the tag.
  4. Approve the pypi environment gate.
  5. Step 8: move the published-release constants and the other surfaces the suite enumerates.

#1127 and the Q2 ledger

  • fix(trust): treat manifest-declared policy packs as trust roots (#1075) #1127 is in. Merge commit 04fc9ce merges main (b581c39) into this branch instead of rebasing, so no force-push was needed. CHANGELOG.md was the only conflict. Both changelog files were regenerated from main's Unreleased section by the same cut script:
  • The Q2 ledger is benchmark/application-q2/results/2026-11-08-04fc9ced.md with its .scores.json. It ran on the development corpus with the release build, 04fc9ce. Every commit after it changes no source.
    • Status: 39 partial, 6 not_established and 4 timeout.
    • Rows: no added, removed or changed row, and 415 not_established candidates.
    • Q0 37/49 (retained), Q1 0/49, Q2 0/49, against 4/49 and 3/49 at the 2026-10-05 ledger. The release line stands as written: Q2: 0/49 development (3/49 at the 2026-10-05 ledger), holdout not yet pinned.
    • All 49 answers equal main's at 952a74c, the run the regression figures quote.
    • run.py exited 1 on the four timeouts. That is recorded in the ledger and does not block the release.
    • Member time sums to 7,982 s, against 1,263 s on 2026-10-05.
  • Test change. test_every_ledger_says_what_its_scores_say now accepts a null answer_id for a member whose row shows it has no answer (timeout, refused or unavailable), and only with Q1 false. This is the first ledger with timeouts. The benchmark README documents it.

Verification

  • Full suite. pytest -m "not perf" -n auto -rfEs ran in a venv built from constraints/dev.txt (pydantic 2.14.3) plus constraints/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 pin tool.version. Fixed in 8ec1c8d, and the test passes.
    • Two cases of test_check_answers_an_unmodelled_settings_key_in_every_format. They fail only on this machine, whose global git ignore hides .claude/settings.local.json from the fixture's commit. The test file is unchanged from main.
  • After fix(trust): treat manifest-declared policy packs as trust roots (#1075) #1127. The files the merge touched pass: the release pipeline, docs links, surface parity, public surface, 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.
  • Schemas. python scripts/generate_schemas.py --check passes under pydantic 2.14.3, with all 15 new documents pinned.
  • Release note. The 1.3.0 section is 12,152 characters, against the 125,000 limit. Every prose line of the old Unreleased section is in docs/changelog/1.3.0.md, and every section below 1.2.0 is byte-identical.

🤖 Generated with Claude Code

- 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
pengfei-threemoonslab merged commit f96f1e9 into main Nov 8, 2026
16 checks passed
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant