Reverts PR #247 (merge f3f9483, MAINT-28) out of release/1.0, so the 19 Nov release ships MAINT-24 + MAINT-25 without MAINT-28. Owner go 2026-11-14.
Why
The rig failed f3f9483 (reports/MAINT-28-test-report.md), and the fix-forward PR #248 review found a High regression (reports/MAINT-28-fix-review-report.md).
## What
Reverts PR #247 (merge f3f9483, MAINT-28) out of `release/1.0`, so the 19 Nov release ships MAINT-24 + MAINT-25 without MAINT-28. Owner go 2026-11-14.
## Why
The rig failed f3f9483 (`reports/MAINT-28-test-report.md`), and the fix-forward PR #248 review found a High regression (`reports/MAINT-28-fix-review-report.md`).
## Proof it is exact
- `git rev-parse HEAD^{tree}` = `8846f0cb3c00d40286a3f1e594f67adf651eb0b7`
- `git rev-parse 1b5f7c9^{tree}` = `8846f0cb3c00d40286a3f1e594f67adf651eb0b7`
- `git diff 1b5f7c9 HEAD` is empty.
The tree equals 1b5f7c9, which passed review, CI and the MAINT-24 rig test. Locally passed: test_maint24, test_maint25, test_safety84, test_peakguard.
No CHANGELOG line for MAINT-28 (it does not ship); the MAINT-28 DECISIONS note leaves with the revert.
MAINT-28 continues on PR #248 after the release.
🤖 Generated with [Claude Code](https://claude.ai/code)
https://claude.ai/code/session_01Bdqr7PiaHcBnzPituu2yTC
Takes PR #247 (f3f9483) out of release/1.0 so the 19 Nov release ships
MAINT-24 + MAINT-25 without MAINT-28. The rig failed f3f9483
(reports/MAINT-28-test-report.md) and the fix-forward PR #248 review found
a High regression (reports/MAINT-28-fix-review-report.md). MAINT-28
continues on PR #248 after the release.
Co-Authored-By: Claude <noreply@anthropic.com>
admin
merged commit 4c0122a8b6 into release/1.02026-11-14 02:35:35 +01:00
Reviewed and merged. One revert commit; tree 8846f0cb equals 1b5f7c9, diff empty; CI 1647/1648 green; no MAINT-28 CHANGELOG line. Merge 4c0122a, tree still 8846f0cb. MAINT-28 continues on #248.
Reviewed and merged. One revert commit; tree 8846f0cb equals 1b5f7c9, diff empty; CI 1647/1648 green; no MAINT-28 CHANGELOG line. Merge 4c0122a, tree still 8846f0cb. MAINT-28 continues on #248.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
Reverts PR #247 (merge
f3f9483, MAINT-28) out ofrelease/1.0, so the 19 Nov release ships MAINT-24 + MAINT-25 without MAINT-28. Owner go 2026-11-14.Why
The rig failed
f3f9483(reports/MAINT-28-test-report.md), and the fix-forward PR #248 review found a High regression (reports/MAINT-28-fix-review-report.md).Proof it is exact
git rev-parse HEAD^{tree}=8846f0cb3c00d40286a3f1e594f67adf651eb0b7git rev-parse 1b5f7c9^{tree}=8846f0cb3c00d40286a3f1e594f67adf651eb0b7git diff 1b5f7c9 HEADis empty.The tree equals
1b5f7c9, which passed review, CI and the MAINT-24 rig test. Locally passed: test_maint24, test_maint25, test_safety84, test_peakguard.No CHANGELOG line for MAINT-28 (it does not ship); the MAINT-28 DECISIONS note leaves with the revert.
MAINT-28 continues on PR #248 after the release.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Bdqr7PiaHcBnzPituu2yTC
Reviewed and merged. One revert commit; tree
8846f0cbequals1b5f7c9, diff empty; CI 1647/1648 green; no MAINT-28 CHANGELOG line. Merge4c0122a, tree still8846f0cb. MAINT-28 continues on #248.