frankenbit/release-toolkit

Fork 0

chore(release): v0.32.0 #472

Merged

bosun merged 1 commit from release-prep/rolling into main

2026-07-07 21:05:10 +02:00

release-bot commented

2026-07-07 20:59:32 +02:00

Member

Added

Adopter-overridable REGISTER_PATTERNS vocabulary in reusable-register-check.yml. A new register_patterns_override input on the reusable accepts a newline-separated pattern list that replaces the release-toolkit-maintainer default vocabulary. When empty, the built-in defaults still apply, so release-toolkit-self and adopters who have not opted in are backwards-compatible.

Motivation: several built-in patterns are common English role words in adopter contexts. They trip the file scan on unrelated adopter prose the moment an adopter uses those words normally. The override lets adopters swap in their own project-specific vocabulary. The scope is a full replacement; an additive mode is not part of this iteration.

The override lands at library level in scripts/lib/register-patterns.sh, so both the PR-time gate and the compose-time bullet scrub in conventional-commits.sh respect the same list. All three scan modes (--file-scan, --git-log, --stdin) apply the override symmetrically. Format: one pattern per line; empty lines ignored; regex metacharacters must be pre-escaped. Closes #435.

Changed

None.

Deprecated

None.

Removed

None.

Fixed

None.

### Added **Adopter-overridable `REGISTER_PATTERNS` vocabulary in `reusable-register-check.yml`**. A new `register_patterns_override` input on the reusable accepts a newline-separated pattern list that replaces the release-toolkit-maintainer default vocabulary. When empty, the built-in defaults still apply, so release-toolkit-self and adopters who have not opted in are backwards-compatible. Motivation: several built-in patterns are common English role words in adopter contexts. They trip the file scan on unrelated adopter prose the moment an adopter uses those words normally. The override lets adopters swap in their own project-specific vocabulary. The scope is a full replacement; an additive mode is not part of this iteration. The override lands at library level in `scripts/lib/register-patterns.sh`, so both the PR-time gate and the compose-time bullet scrub in `conventional-commits.sh` respect the same list. All three scan modes (`--file-scan`, `--git-log`, `--stdin`) apply the override symmetrically. Format: one pattern per line; empty lines ignored; regex metacharacters must be pre-escaped. Closes [#435](https://git.frankenbit.de/frankenbit/release-toolkit/issues/435). ### Changed None. ### Deprecated None. ### Removed None. ### Fixed None.

release-bot added 1 commit

2026-07-07 20:59:32 +02:00

chore(release): prepare v0.32.0

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

Details

check-self-bootstrap / check (pull_request) Has been skipped

Details

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

Details

fragment-check / changelog fragment-kind (pull_request) Successful in 3s

Details

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

Details

manifest-check / manifest-vs-tag consistency (pull_request) Successful in 5s

Details

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

Details

tests / bats (pull_request) Successful in 1m58s

Details

tests / shellcheck (pull_request) Successful in 8s

Details

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

Details

release / decide + act (push) Successful in 6s

Details

release / release (push) Successful in 0s

Details

tests / bats (push) Successful in 1m58s

Details

tests / shellcheck (push) Successful in 8s

Details

mirror-on-cut / mirror-1 (release) Successful in 1s

Details

mirror-on-cut / mirror (release) Successful in 0s

Details

78d80446bb

Generated by release-toolkit release-prep.sh.

Tracker: frankenbit/release-toolkit#1

surveyor approved these changes

2026-07-07 21:04:39 +02:00

surveyor left a comment

APPROVED — PR#472 @ `78d8044` (chore(release): v0.32.0 — #435, fold-3 arc-close)

Clean rolling cut-prep. Verified the composition on-source and CI green by-SHA. This is #448 EP-4 and the fold-3 arc-close cut.

Composition — correct

VERSION = 0.32.0 — minor bump, correct: #435 is kind=added (feat → MINOR), 0.31.0 → 0.32.0.
CHANGELOG ### Added ← #435 (adopter-overridable REGISTER_PATTERNS). Correct kind-section; 6-header scaffolding with None.; Closes #435. The prose accurately captures the verified properties — library-level override so both the PR-time gate and compose-time bullet scrub respect one list, and all three scan modes (--file-scan/--git-log/--stdin) apply it symmetrically. Matches what I behaviorally proved on the #435 review.
Fragment 435.added.md consumed. changelog-body-check (+ Cold-Read linter) green.

Cut substrate — bake / float / override all correct

5 reusables baked BUILD_BAKED_TOOLKIT_REF: 'v0.32.0' (#336 adopter freeze).
All 5 toolkit-self wrappers float uses:@main (incl. asymmetric fragment-check.yml → reusable-changelog-fragment-check.yml@main) — auto-re-pin @main-skip held.
#460 override intact in reusable-release.yml (1 hit).
Adopter examples re-pinned @v0.32.0; no stale 0.31.0 refs in README/docs/examples.
On current main (merge_base == tip 9f568ae) — no cross-PR composition concern this time.

CI

Green by-SHA: 11/11 success. Composition reproduced locally; nothing red.

Clean to merge → v0.32.0 cut = EP-4, fold-3 arc-close. This brings the #448 adversarial-multi-cut AC to four clean cuts on the floated substrate (v0.30.2 / v0.30.3 / v0.31.0 / v0.32.0) — into the "several cuts observed" runway that closes the operator-refined AC.

— Surveyor

## APPROVED — PR#472 @ `78d8044` (chore(release): v0.32.0 — #435, fold-3 arc-close) Clean rolling cut-prep. Verified the composition on-source and CI green by-SHA. This is #448 EP-4 and the fold-3 arc-close cut. ### Composition — correct - **VERSION = 0.32.0** — minor bump, correct: #435 is `kind=added` (feat → MINOR), 0.31.0 → 0.32.0. - **CHANGELOG `### Added`** ← #435 (adopter-overridable `REGISTER_PATTERNS`). Correct kind-section; 6-header scaffolding with `None.`; `Closes #435`. The prose accurately captures the verified properties — library-level override so both the PR-time gate and compose-time bullet scrub respect one list, and all three scan modes (`--file-scan`/`--git-log`/`--stdin`) apply it symmetrically. Matches what I behaviorally proved on the #435 review. - Fragment `435.added.md` consumed. changelog-body-check (+ Cold-Read linter) green. ### Cut substrate — bake / float / override all correct - 5 reusables baked `BUILD_BAKED_TOOLKIT_REF: 'v0.32.0'` (#336 adopter freeze). - All 5 toolkit-self wrappers float `uses:@main` (incl. asymmetric `fragment-check.yml → reusable-changelog-fragment-check.yml@main`) — auto-re-pin `@main`-skip held. - #460 override intact in `reusable-release.yml` (1 hit). - Adopter examples re-pinned `@v0.32.0`; no stale `0.31.0` refs in README/docs/examples. - On current main (merge_base == tip `9f568ae`) — no cross-PR composition concern this time. ### CI Green by-SHA: 11/11 success. Composition reproduced locally; nothing red. Clean to merge → v0.32.0 cut = EP-4, fold-3 arc-close. This brings the #448 adversarial-multi-cut AC to **four** clean cuts on the floated substrate (v0.30.2 / v0.30.3 / v0.31.0 / v0.32.0) — into the "several cuts observed" runway that closes the operator-refined AC. — Surveyor