frankenbit/release-toolkit

Fork 0

chore(readme): point the adopter pin at the newest servable release #1400

Merged

bosun merged 1 commit from chore/readme-pin-20260906231245 into main

2026-09-07 01:32:39 +02:00

release-bot commented

2026-09-07 01:12:46 +02:00

Member

Opened by mirror-release.yml after a successful mirror publish (release-toolkit#1378). The adopter-facing pins in README.md, docs/integration.md and examples/** are set by the MIRROR rather than by the cut, because only the mirror knows when a version becomes fetchable. rt readme-pin-check --fix computed the target with the same code that grades it. Read the diff: this changes what a stranger is told to pin.

no-changelog: docs currency -- this PR only re-points adopter pins at the release that just published, and a fragment here would describe that release in the NEXT one's notes.

Opened by `mirror-release.yml` after a successful mirror publish (release-toolkit#1378). The adopter-facing pins in `README.md`, `docs/integration.md` and `examples/**` are set by the MIRROR rather than by the cut, because only the mirror knows when a version becomes fetchable. `rt readme-pin-check --fix` computed the target with the same code that grades it. Read the diff: this changes what a stranger is told to pin. no-changelog: docs currency -- this PR only re-points adopter pins at the release that just published, and a fragment here would describe that release in the NEXT one's notes.

release-bot added 1 commit

2026-09-07 01:12:46 +02:00

chore(readme): point the adopter pin at the newest servable release (#1378 )

toolkit-self-gates / toolkit-self gates (PR's own rt) (pull_request) Successful in 8s

Details

fragment-check / check (pull_request) Successful in 0s

Details

ac-closure-check / check (pull_request) Successful in 0s

Details

changelog-body-check / changelog body Cold-Read linter (pull_request) Successful in 49s

Details

changelog-body-check / check (pull_request) Successful in 0s

Details

tests / dated-examples (pull_request) Successful in 32s

Details

go-ci / lint + build + test (pull_request) Successful in 1m8s

Details

go-ci / page landing-tree failure (pull_request) Has been skipped

Details

workflow-parse-check / toolkit-self parse guard and controls (pull_request) Successful in 29s

Details

workflow-parse-check / workflow parse and schema (pull_request) Successful in 29s

Details

workflow-parse-check / check (pull_request) Successful in 0s

Details

tests / bats (pull_request) Successful in 1m22s

Details

gitea-twin-check / check (push) Successful in 6s

Details

go-ci / record reviewed vs landed commit (push) Successful in 3s

Details

prepared-uncut-check / toolkit-self prepared-uncut controls (push) Successful in 6s

Details

tests / workflow-schema (push) Successful in 4s

Details

tests / dated-examples (push) Successful in 5s

Details

check-self-bootstrap / check (push) Successful in 27s

Details

tests / shellcheck (push) Successful in 4s

Details

tests / contract-paths (push) Successful in 27s

Details

prepared-uncut-check / prepared-but-uncut release (push) Successful in 52s

Details

prepared-uncut-check / check (push) Successful in 0s

Details

go-ci / lint + build + test (push) Successful in 1m9s

Details

go-ci / page landing-tree failure (push) Has been skipped

Details

release / decide + act (push) Successful in 1m14s

Details

release / release (push) Successful in 0s

Details

release / fire-cut (push) Has been skipped

Details

tests / bats (push) Successful in 1m19s

Details

8d207d744f

shipwright referenced this pull request from a commit

2026-09-07 01:22:50 +02:00

fix(readme): assert no mirror state the page cannot keep true

surveyor approved these changes

2026-09-07 01:25:22 +02:00

surveyor left a comment

APPROVE — reviewed at 8d207d744f13c4347ee8de155d94019a85fe6137, base clean (behind 0, merge-base = 99cf4998 = main).

This PR is the production verification of `#1393` and `#1394`, and both hold

#1393  the PR is GRADED          79 status rows over 2 pages, paginated to an EMPTY page
                                 28 contexts · REQUIRED NOT GREEN: 0
                                 (the last bot pin PR, #1391, carried ZERO)
#1394  the JOB wrote the body    "no-changelog: docs currency -- this PR only re-points
                                 adopter pins at the release that just published…"
                                 author: release-bot — not a hand-written unblock

🔑 Both fixes were argued from a single measured instance and a census, and this is the first exercise that could have refuted either. Neither did. That is the read I would have wanted before those merged and could not have had.

The content

removed @v0.62.0   19
added   @v0.62.1   19
changed lines that are NOT a pin move   0

✅ And the property the pins depend on is answered by the instrument authoritative for it, not by my reading: readme-pin-check / check is success on this head. The pins may only name a version a stranger can actually fetch, and the code that computes the target is the code that grades it.

On the rc=1 you are seeing on main

📌 That is the gate reporting currency, not correctness, and its own message says so — "19 divergence(s), 0 of which break a stranger." You dispatched the mirror, the mirror moved, and the pins trail it until this lands. ⚠️ Worth stating plainly for whoever reads main's board in the meantime: a red readme-pin-check on main between a mirror dispatch and its pin PR is the expected steady state, not a defect — and it is exactly the window this PR closes.

Nothing outstanding. #1409 next, since it rebases onto this.

**APPROVE** — reviewed at `8d207d744f13c4347ee8de155d94019a85fe6137`, base clean (behind 0, merge-base = `99cf4998` = main). ## This PR is the production verification of `#1393` and `#1394`, and both hold ``` #1393 the PR is GRADED 79 status rows over 2 pages, paginated to an EMPTY page 28 contexts · REQUIRED NOT GREEN: 0 (the last bot pin PR, #1391, carried ZERO) #1394 the JOB wrote the body "no-changelog: docs currency -- this PR only re-points adopter pins at the release that just published…" author: release-bot — not a hand-written unblock ``` 🔑 **Both fixes were argued from a single measured instance and a census, and this is the first exercise that could have refuted either. Neither did.** *That is the read I would have wanted before those merged and could not have had.* ## The content ``` removed @v0.62.0 19 added @v0.62.1 19 changed lines that are NOT a pin move 0 ``` ✅ **And the property the pins depend on is answered by the instrument authoritative for it, not by my reading:** `readme-pin-check / check` is **`success`** on this head. **The pins may only name a version a stranger can actually fetch, and the code that computes the target is the code that grades it.** ## On the rc=1 you are seeing on main 📌 **That is the gate reporting currency, not correctness, and its own message says so** — *"19 divergence(s), 0 of which break a stranger."* **You dispatched the mirror, the mirror moved, and the pins trail it until this lands.** ⚠️ **Worth stating plainly for whoever reads main's board in the meantime: a red `readme-pin-check` on main between a mirror dispatch and its pin PR is the expected steady state, not a defect** — and it is exactly the window this PR closes. **Nothing outstanding. `#1409` next, since it rebases onto this.**

bosun merged commit 8d207d744f into main

2026-09-07 01:32:39 +02:00

bosun deleted branch chore/readme-pin-20260906231245

2026-09-07 01:32:39 +02:00

forgejo-actions commented

2026-09-07 01:32:48 +02:00

Landing identity record

PR: #1400
landed commit (server merge_commit_sha): 8d207d744f13c4347ee8de155d94019a85fe6137
effective official approval(s):
- @surveyor, review #6858, stamped commit: 8d207d744f13c4347ee8de155d94019a85fe6137
replay comparison: no identity change (stamped SHA equals landed SHA)

This is a post-merge identity record. It does not retroactively review the landed object; it records whether the server landed the object that an official approval named.

## Landing identity record - PR: #1400 - landed commit (server merge_commit_sha): `8d207d744f13c4347ee8de155d94019a85fe6137` - effective official approval(s): - @surveyor, review #6858, stamped commit: `8d207d744f13c4347ee8de155d94019a85fe6137` - replay comparison: no identity change (stamped SHA equals landed SHA) This is a post-merge identity record. It does not retroactively review the landed object; it records whether the server landed the object that an official approval named.