chore(release): v0.47.0 #891

Merged

alex merged 1 commit from release-prep/rolling into main 2026-08-26 13:53:44 +02:00

Conversation 0 Commits 1 Files changed 24 +88 -50

release-bot commented 2026-08-26 12:55:57 +02:00

Member

Copy link

Changelog density — clean

• WARN — check 7 (sentence length): sentence(s) between 25–30 words — consider splitting (https://git.frankenbit.de/frankenbit/release-toolkit/src/branch/main/docs/conventions.md#writing-adopter-facing-prose)
  • 27w: The asymmetry #662 quoted — 'rt decide' reporting 'mode=cut' for a run...
  • 27w: It runs against a scratch copy and prints the diff it would produce, s...
• 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

• contract source-of-record split: byte-authority and provenance are now separate fields, and both are checkable (#849)

  The single field carried two different claims, so a naive check reddened on six correct sites. Source of record now lists only paths that must resolve today. Ported from lists historical paths, checked for having ever existed. scripts/contract-paths-check.sh grades both halves and classifies globs rather than resolving them.

Fixed

• cut-cancellation recovery docs: recovery (A) now covers manifest-create, non-atomicity, and the published-release case (#660)

  docs/integration.md § Cut-cancellation recovery (#417) no longer says "edit" the manifest for adopters who never had one — it gives the full create-from-scratch JSON. The three (A) steps are now named as non-atomic, since a bare tag push can silently clear the bootstrap population's orphan check unfinished. (B) is flagged as actively wrong once a release is already published, per the live 2026-08-25 incident (#884).

• dry-run preview docs: fix the fidelity-guarantee direction and two stale claims (#662)

  The asymmetry #662 quoted — rt decide reporting mode=cut for a run that would resolve mode=update live — was already closed at the code level by #689. The doc now says so plainly: --dry-run is a computational no-op for rt decide. Also retires the stale FORGEJO_API_DRY_RUN env-var reference and names a live gap: rt release's idempotency pre-check is faked under --dry-run, always previewing a create.

• changelog: suppress duplicate commit bullets covered by body-referenced fragments (#672)

  Multi-commit changes can keep the richer fragment entry without widening the add-only fragment walk that protects against silent omission.

• release: disclose whether post-cut manifest bookkeeping creates or updates (#679)

  The typed post-cut boundary now preserves the observable create/update branch evidence from the release workflow.

• prep: rt prep --dry-run no longer writes your checkout. It runs against a scratch copy and prints the diff it would produce, so a failed run leaves nothing behind for the retry's clean-tree gate to refuse. post_bump_hooks run in the scratch copy; anything they touch outside their working directory is still not contained (#708)

• decide: a cut-safeguard that declines no longer resolves to mode=noop when the fall-through finds nothing release-relevant. That path dropped safeguard_fail, safeguard_version and prep_sha and exited 0, so a decline read exactly like "nothing to release". It now emits mode=blocked with reason=safeguard_decline, which the workflow already fails on. A could-not-grade stays distinguishable from a refusal (#711)

• operations: document drain-before-review order for rolling release PRs (#770)

  Land other work before reviewing the rolling PR, then merge it before another main landing can rebuild its content and invalidate the approval. This is a regeneration rule, not an outdated-branch rule.

• manifest: a draft cut no longer records a completed release. Schema 2 adds last_released_published, so a cut that leaves the release unpublished says so. manifest-check now reports the absent tag as an unfinished cut, not a desync. Schema 1 is still read, and migrates only when a record needs the new field (#805)

• 849: fragment density, and scrub a register over-match in the arms

• ci: keep the blocked arm FLAT so its bats guard reads what it means to

Removed

None.

Deprecated

None.

Upgrade

None.

Internal

• test guards: make pending-cut branch extraction safe for nested shell cases (#889)

  The workflow contract is unchanged; the structural guard now proves both a nested-case success path and a missing-refusal inverse fails closed.

<!-- rt:density-verdict --> ### Changelog density — clean - **WARN** — check 7 (sentence length): sentence(s) between 25–30 words — consider splitting (https://git.frankenbit.de/frankenbit/release-toolkit/src/branch/main/docs/conventions.md#writing-adopter-facing-prose) - `27w: The asymmetry #662 quoted — 'rt decide' reporting 'mode=cut' for a run...` - `27w: It runs against a scratch copy and prints the diff it would produce, s...` - **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 - **contract source-of-record split**: byte-authority and provenance are now separate fields, and both are checkable (#849) The single field carried two different claims, so a naive check reddened on six correct sites. `Source of record` now lists only paths that must resolve today. `Ported from` lists historical paths, checked for having ever existed. `scripts/contract-paths-check.sh` grades both halves and classifies globs rather than resolving them. ### Fixed - **cut-cancellation recovery docs**: recovery (A) now covers manifest-create, non-atomicity, and the published-release case (#660) `docs/integration.md § Cut-cancellation recovery (#417)` no longer says "edit" the manifest for adopters who never had one — it gives the full create-from-scratch JSON. The three (A) steps are now named as non-atomic, since a bare tag push can silently clear the bootstrap population's orphan check unfinished. (B) is flagged as actively wrong once a release is already published, per the live 2026-08-25 incident (#884). - **dry-run preview docs**: fix the fidelity-guarantee direction and two stale claims (#662) The asymmetry #662 quoted — `rt decide` reporting `mode=cut` for a run that would resolve `mode=update` live — was already closed at the code level by #689. The doc now says so plainly: `--dry-run` is a computational no-op for `rt decide`. Also retires the stale `FORGEJO_API_DRY_RUN` env-var reference and names a live gap: `rt release`'s idempotency pre-check is faked under `--dry-run`, always previewing a create. - **changelog**: suppress duplicate commit bullets covered by body-referenced fragments (#672) Multi-commit changes can keep the richer fragment entry without widening the add-only fragment walk that protects against silent omission. - **release**: disclose whether post-cut manifest bookkeeping creates or updates (#679) The typed post-cut boundary now preserves the observable create/update branch evidence from the release workflow. - **prep**: `rt prep --dry-run` no longer writes your checkout. It runs against a scratch copy and prints the diff it would produce, so a failed run leaves nothing behind for the retry's clean-tree gate to refuse. `post_bump_hooks` run in the scratch copy; anything they touch outside their working directory is still not contained (#708) - **decide**: a cut-safeguard that declines no longer resolves to `mode=noop` when the fall-through finds nothing release-relevant. That path dropped `safeguard_fail`, `safeguard_version` and `prep_sha` and exited 0, so a decline read exactly like "nothing to release". It now emits `mode=blocked` with `reason=safeguard_decline`, which the workflow already fails on. A could-not-grade stays distinguishable from a refusal (#711) - **operations**: document drain-before-review order for rolling release PRs (#770) Land other work before reviewing the rolling PR, then merge it before another main landing can rebuild its content and invalidate the approval. This is a regeneration rule, not an outdated-branch rule. - **manifest**: a draft cut no longer records a completed release. Schema 2 adds `last_released_published`, so a cut that leaves the release unpublished says so. `manifest-check` now reports the absent tag as an unfinished cut, not a desync. Schema 1 is still read, and migrates only when a record needs the new field (#805) - **849**: fragment density, and scrub a register over-match in the arms - **ci**: keep the blocked arm FLAT so its bats guard reads what it means to ### Removed None. ### Deprecated None. ### Upgrade None. ### Internal - **test guards**: make pending-cut branch extraction safe for nested shell cases (#889) The workflow contract is unchanged; the structural guard now proves both a nested-case success path and a missing-refusal inverse fails closed.

release-bot added 1 commit 2026-08-26 12:55:57 +02:00

chore(release): prepare v0.46.2 ... 2ede7aecd2

Generated by release-toolkit rt prep.

Tracker: frankenbit/release-toolkit#1

release-bot force-pushed release-prep/rolling from 2ede7aecd2 to 949b77cb3f 2026-08-26 13:09:39 +02:00 Compare

release-bot changed title from chore(release): v0.46.2 to chore(release): v0.47.0 2026-08-26 13:20:35 +02:00

release-bot force-pushed release-prep/rolling from 949b77cb3f to 1789f96e01 2026-08-26 13:20:37 +02:00 Compare

release-bot force-pushed release-prep/rolling from 1789f96e01 to d36dcc5db6 2026-08-26 13:20:51 +02:00 Compare

release-bot force-pushed release-prep/rolling from d36dcc5db6 to c4a5d38946 2026-08-26 13:21:27 +02:00 Compare

release-bot force-pushed release-prep/rolling from c4a5d38946 to f6429660a9 2026-08-26 13:26:10 +02:00 Compare

release-bot force-pushed release-prep/rolling from f6429660a9 to 2aaf440ea0 2026-08-26 13:28:35 +02:00 Compare

rigger referenced this pull request 2026-08-26 13:33:08 +02:00

docs(operations): serialize rolling PR drain rule (#770) #901

rigger referenced this pull request 2026-08-26 13:33:25 +02:00

bug(release): the rolling PR regenerates on every merge, so its reviewer pays for other landings #770

release-bot force-pushed release-prep/rolling from 2aaf440ea0 to 2605f12236 2026-08-26 13:42:14 +02:00 Compare

release-bot force-pushed release-prep/rolling from 2605f12236 to e4a3206d33 2026-08-26 13:42:54 +02:00 Compare

release-bot force-pushed release-prep/rolling from e4a3206d33 to 239b5063c9 2026-08-26 13:49:57 +02:00 Compare

alex merged commit 239b5063c9 into main 2026-08-26 13:53:44 +02:00

alex deleted branch release-prep/rolling 2026-08-26 13:53:45 +02:00

Sign in to join this conversation.

Reviewers

No reviewers

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

1 participant

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!891

No description provided.