chore(release): v0.62.3 #1429

Merged

bosun merged 1 commit from release-prep/rolling into main 2026-09-07 09:26:47 +02:00

Conversation 2 Commits 1 Files changed 23 +51 -48

release-bot commented 2026-09-07 08:45:59 +02:00

Member

Copy link

Changelog density — clean

• PASS — check 7 (sentence length): all sentences ≤ 25 words. Lists, tables and blockquotes are measured too (#632).
• PASS — check 8 (paren nesting): all paragraphs ≤ depth 2
• PASS — check 9 (paragraph length): all paragraphs ≤ 75 words. Lists, tables and blockquotes are measured too (#632).

Advisory mirror of the cut-time gate, computed when this description was written. It carries no authority: the cut re-runs these checks against the section as it stands then, and this branch is recreated from main on every compose.

Added

None.

Changed

None.

Fixed

None.

Removed

None.

Deprecated

None.

Upgrade

None.

Internal

• internal: an arm holds the README Status rule (#1401).
• docs: the integration guide answers its hardest questions where a reader can reach them (#1407)
• internal: the integration guide names no ungraded version (#1415).

<!-- rt:density-verdict --> ### Changelog density — clean - **PASS** — check 7 (sentence length): all sentences ≤ 25 words. Lists, tables and blockquotes are measured too (#632). - **PASS** — check 8 (paren nesting): all paragraphs ≤ depth 2 - **PASS** — check 9 (paragraph length): all paragraphs ≤ 75 words. Lists, tables and blockquotes are measured too (#632). _Advisory mirror of the cut-time gate, computed when this description was written._ _It carries no authority: the cut re-runs these checks against the section as it stands then, and this branch is recreated from `main` on every compose._ <!-- /rt:density-verdict --> ### Added None. ### Changed None. ### Fixed None. ### Removed None. ### Deprecated None. ### Upgrade None. ### Internal - **internal**: an arm holds the README Status rule (#1401). - **docs**: the integration guide answers its hardest questions where a reader can reach them (#1407) - **internal**: the integration guide names no ungraded version (#1415).

release-bot added 1 commit 2026-09-07 08:45:59 +02:00

chore(release): prepare v0.62.3 ... a015489248

Generated by release-toolkit rt prep.

Tracker: frankenbit/release-toolkit#1

release-bot requested review from surveyor 2026-09-07 08:45:59 +02:00

release-bot force-pushed release-prep/rolling from a015489248 to d4917b7222 2026-09-07 09:13:50 +02:00 Compare

surveyor approved these changes 2026-09-07 09:24:21 +02:00

surveyor left a comment

Copy link

APPROVED at head d4917b7222305f8c519ab2e92cf4fb67813e969b. Routine cut, verified rather than pattern-matched.

The cut is current, which is the check a rolling branch actually needs

merge-base(origin/main, cut)  cbf70184   == origin/main   -> the cut is NOT behind
cbf70184 is an ancestor of the cut                        -> #1430 IS included
VERSION   0.62.2 -> 0.62.3

Fragments consumed, and the remainder is infrastructure only

consumed (deleted)  1401-an-arm-holds-the-status-rule · 1407-guide-start-here
                    1415-the-guide-names-no-ungraded-version
left in changelog.d/  .keep · .template.md      <- zero real fragments stranded
CHANGELOG            3 Internal entries, one per consumed fragment

The build-ref bump, swept UNFILTERED over the resulting tree

This is an absence claim — no marker left at main — so it is graded over the whole state, not over the diff:

18 markers found (9 in .forgejo/workflows, 9 in .gitea/workflows — symmetric)
distinct values:  18 x 'v0.62.3'      occurrences of 'main': 0
VERSION agrees: 0.62.3

✅ Positive control, run against origin/main where the value is known to be unbumped: 18 x 'main'. The sweep can see the thing whose absence I am claiming, so the zero is a measurement rather than a silent miss.

Required set by complement

enable_status_check=true · required 23 · 168 status rows paginated to an EMPTY page (p=5)
28 distinct contexts · REQUIRED NOT GREEN: 0 · non-success rows of any kind: 0
gitea-twin-check / check (pull_request)   success

🔑 A wrong instrument I ran and am reporting rather than burying

I byte-compared the 11 shared .forgejo/.gitea filenames and got identical: 0, differing: 11. ⚠️ That is the EXPECTED state, not a finding — a .gitea twin references .gitea paths by construction, so byte-identity is the wrong invariant and my check would have manufactured an accusation out of correct work.

📌 gitea-twin-check is the gate that grades the real invariant, it is in the required set, and it is green. This is /srv/CLAUDE.md's a check you wrote yourself when a gate already grades that property row, and the tell it names fired exactly as written: I was about to compare artefacts that are GENERATED. Invoke the gate; do not re-derive its spec from its output.

⚠️ One nit, and it is mine

- **internal**: an arm holds the README Status rule (#1401).          <- period
- **docs**: … where a reader can reach them (#1407)                   <- NO period
- **internal**: the integration guide names no ungraded version (#1415).  <- period

The generator copied the fragment faithfully; the fragment 1407-guide-start-here.internal.md has no trailing period. 📌 That fragment came in on #1430, which I approved ninety minutes ago — so this reached the release CHANGELOG through my own stamp. ✅ Not blocking and not worth a re-cut: changelog-body-check is green, so it violates no rule, and a released CHANGELOG line is not worth re-spinning a cut over. Recorded so it is fixed at the source rather than in the generated file.

---

📌 For whoever merges — the one thing this stamp cannot cover

release-prep/rolling is force-pushed on every base move, which dismisses stamps. d4917b72 is current as I write. 🔴 Compare this stamp's commit_id against the head AT THE MOMENT YOU MERGE — stale will not tell you, because a pure rebase onto a base that does not touch these paths leaves stale=false while the head moves underneath. ⚠️ And pass delete_branch_after_merge:false — this branch must survive.

**APPROVED at head `d4917b7222305f8c519ab2e92cf4fb67813e969b`.** Routine cut, verified rather than pattern-matched. ## The cut is current, which is the check a rolling branch actually needs ``` merge-base(origin/main, cut) cbf70184 == origin/main -> the cut is NOT behind cbf70184 is an ancestor of the cut -> #1430 IS included VERSION 0.62.2 -> 0.62.3 ``` ## Fragments consumed, and the remainder is infrastructure only ``` consumed (deleted) 1401-an-arm-holds-the-status-rule · 1407-guide-start-here 1415-the-guide-names-no-ungraded-version left in changelog.d/ .keep · .template.md <- zero real fragments stranded CHANGELOG 3 Internal entries, one per consumed fragment ``` ## The build-ref bump, swept UNFILTERED over the resulting tree **This is an absence claim — *no marker left at `main`* — so it is graded over the whole state, not over the diff:** ``` 18 markers found (9 in .forgejo/workflows, 9 in .gitea/workflows — symmetric) distinct values: 18 x 'v0.62.3' occurrences of 'main': 0 VERSION agrees: 0.62.3 ``` ✅ **Positive control, run against `origin/main` where the value is known to be unbumped:** `18 x 'main'`. **The sweep can see the thing whose absence I am claiming**, so the zero is a measurement rather than a silent miss. ## Required set by complement ``` enable_status_check=true · required 23 · 168 status rows paginated to an EMPTY page (p=5) 28 distinct contexts · REQUIRED NOT GREEN: 0 · non-success rows of any kind: 0 gitea-twin-check / check (pull_request) success ``` ## 🔑 A wrong instrument I ran and am reporting rather than burying **I byte-compared the 11 shared `.forgejo`/`.gitea` filenames and got `identical: 0, differing: 11`.** ⚠️ **That is the EXPECTED state, not a finding** — a `.gitea` twin references `.gitea` paths by construction, so byte-identity is the wrong invariant and my check would have manufactured an accusation out of correct work. 📌 **`gitea-twin-check` is the gate that grades the real invariant, it is in the required set, and it is green.** **This is `/srv/CLAUDE.md`'s *a check you wrote yourself when a gate already grades that property* row, and the tell it names fired exactly as written: I was about to compare artefacts that are GENERATED.** *Invoke the gate; do not re-derive its spec from its output.* ## ⚠️ One nit, and it is mine ``` - **internal**: an arm holds the README Status rule (#1401). <- period - **docs**: … where a reader can reach them (#1407) <- NO period - **internal**: the integration guide names no ungraded version (#1415). <- period ``` **The generator copied the fragment faithfully; the fragment `1407-guide-start-here.internal.md` has no trailing period.** 📌 **That fragment came in on `#1430`, which I approved ninety minutes ago — so this reached the release CHANGELOG through my own stamp.** ✅ **Not blocking and not worth a re-cut: `changelog-body-check` is green, so it violates no rule, and a released CHANGELOG line is not worth re-spinning a cut over.** *Recorded so it is fixed at the source rather than in the generated file.* --- ## 📌 For whoever merges — the one thing this stamp cannot cover **`release-prep/rolling` is force-pushed on every base move, which dismisses stamps.** *`d4917b72` is current as I write.* 🔴 **Compare this stamp's `commit_id` against the head AT THE MOMENT YOU MERGE** — `stale` will not tell you, because a pure rebase onto a base that does not touch these paths leaves `stale=false` while the head moves underneath. ⚠️ **And pass `delete_branch_after_merge:false` — this branch must survive.**

bosun merged commit d4917b7222 into main 2026-09-07 09:26:47 +02:00

forgejo-actions commented 2026-09-07 09:26:59 +02:00

Copy link

Landing identity record

• PR: #1429
• landed commit (server merge_commit_sha): d4917b7222305f8c519ab2e92cf4fb67813e969b
• effective official approval(s):
  • @surveyor, review #6905, stamped commit: d4917b7222305f8c519ab2e92cf4fb67813e969b
• 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.

<!-- release-toolkit:landing-review-record-v1 landed=d4917b7222305f8c519ab2e92cf4fb67813e969b --> ## Landing identity record - PR: #1429 - landed commit (server merge_commit_sha): `d4917b7222305f8c519ab2e92cf4fb67813e969b` - effective official approval(s): - @surveyor, review #6905, stamped commit: `d4917b7222305f8c519ab2e92cf4fb67813e969b` - 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.

Sign in to join this conversation.

Reviewers

No reviewers

surveyor

Labels

Clear labels   

bump

major

Override the cut bump to MAJOR (release-toolkit#107)

  

bump

minor

Override the cut bump to MINOR (release-toolkit#107)

  

bump

patch

Override the cut bump to PATCH (release-toolkit#107)

  

kind/bug

Something is broken

  

kind/chore

Maintenance, tooling, refactor

  

kind/docs

Documentation work

  

kind/feature

New feature or capability

  

priority/critical

Critical: must be addressed immediately

  

priority/high

Important, should be addressed soon

  

priority/low

Low priority, address when convenient

  

priority/medium

Normal priority

  

size/L

Large: significant feature, ~6-16h

  

size/M

Medium: moderate feature, ~2-6h

  

size/S

Small: simple change, ~1-2h

  

size/XL

Extra large: major feature or refactor, 16h+

No labels

bump

major

bump

minor

bump

patch

kind/bug

kind/chore

kind/docs

kind/feature

priority/critical

priority/high

priority/low

priority/medium

size/L

size/M

size/S

size/XL

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

3 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

frankenbit/release-toolkit!1429

No description provided.