chore(release): v0.33.0 #484

Merged

alex merged 1 commit from release-prep/rolling into main 2026-07-24 01:28:45 +02:00

Conversation 1 Commits 1 Files changed 20 +60 -29

release-bot commented 2026-07-08 14:06:01 +02:00

Member

Copy link

Added

• build-c4 workflow: LikeC4 static-site build for docs/architecture/c4/**/*.likec4, deployed to arch.saratow.net LAN-only (alcatraz-infra#128 substrate). Consumes tmux-tell#617 forgejo-runner /output bind-mount; served RO via ingress nginx. Refs release-toolkit#367.

• fragment style guide + length-warn CI signal — new docs/fragment-style.md codifies the skim-scan shape a good changelog fragment takes (six rules + before/after examples grounded on the ember v0.3.0/v0.5.0/v0.6.0 recoveries); reusable-changelog-fragment-check.yml gains a fragment_length_warn_chars input (default 500) that emits a non-blocking ::warning:: for fragments exceeding the threshold and points contributors at the guide (#488)

Changed

None.

Fixed

• PREP_SUBJECT_RE now accepts the Forgejo squash-merge subject suffix (#NN). A prep-PR squash-merged on Forgejo produces the commit subject chore(release): vX.Y.Z (#NN) (PR-number appended to the title); the $ anchor previously rejected it, silently skip-gating the cut. #331 made prepare optional for squash-merge but missed the suffix half — measured on ember v0.1.0 (chore(release): v0.1.0 (#37)). The trailing group is added at the end, so BASH_REMATCH[2] version extraction is unaffected. Closes #487.

• Let the changelog fragment PR gate accept a consumer-provided valid-kind list so it can match the repository's release-time assembler instead of hardcoding release-toolkit's own internal convention (#489).

• release-prep no longer emits conventional-commit summary bullets that duplicate an authored changelog fragment. cc_categorize_commits_since now takes an optional fragments-directory argument and suppresses the CC subject bullet of any commit that itself added a fragment in the same range (git log --diff-filter=A), keyed on git commit identity rather than on a shared #NNN prose reference. This catches the ref-absent and ref-mismatched duplicates that changelog_dedup_cc_by_fragment_refs (which keys on the fragment filename id) structurally cannot, and it cannot silently drop genuinely-new content: a change with no fragment sits on a commit the suppression set never contains. The ref-based dedup is retained for the complementary separate-commit-same-ref case. Refs release-toolkit#493 (Bug 2).

• release-prep no longer drops the ### Upgrade section or concatenates a stray None. placeholder onto real content when composing a release over pre-existing ## [Unreleased] content. changelog_merge_sections now sources its section order from the single-source-of-truth CHANGELOG_STANDARD_SECTIONS (so no hand-maintained order list can drift and drop a section) and treats the scaffold None. as a soft-empty sentinel that yields to real content but persists when a kind is empty in every input. Refs release-toolkit#493 (Bug 1).

• fragment-style: scrub '[reviewer]' invented-jargon per register-check gate

• fragment-style: scrub 3 chamber-name attributions per register-check gate

Removed

None.

Deprecated

None.

Upgrade

None.

### Added - `build-c4` workflow: LikeC4 static-site build for `docs/architecture/c4/**/*.likec4`, deployed to `arch.saratow.net` LAN-only (alcatraz-infra#128 substrate). Consumes tmux-tell#617 forgejo-runner `/output` bind-mount; served RO via ingress nginx. Refs release-toolkit#367. - **fragment style guide + length-warn CI signal** — new [`docs/fragment-style.md`](docs/fragment-style.md) codifies the skim-scan shape a good changelog fragment takes (six rules + before/after examples grounded on the ember v0.3.0/v0.5.0/v0.6.0 recoveries); `reusable-changelog-fragment-check.yml` gains a `fragment_length_warn_chars` input (default 500) that emits a non-blocking `::warning::` for fragments exceeding the threshold and points contributors at the guide (#488) ### Changed None. ### Fixed - `PREP_SUBJECT_RE` now accepts the Forgejo squash-merge subject suffix ` (#NN)`. A prep-PR squash-merged on Forgejo produces the commit subject `chore(release): vX.Y.Z (#NN)` (PR-number appended to the title); the `$` anchor previously rejected it, silently skip-gating the cut. #331 made `prepare` optional for squash-merge but missed the suffix half — measured on ember v0.1.0 (`chore(release): v0.1.0 (#37)`). The trailing group is added at the end, so `BASH_REMATCH[2]` version extraction is unaffected. Closes #487. - Let the changelog fragment PR gate accept a consumer-provided valid-kind list so it can match the repository's release-time assembler instead of hardcoding release-toolkit's own `internal` convention (#489). - `release-prep` no longer emits conventional-commit summary bullets that duplicate an authored changelog fragment. `cc_categorize_commits_since` now takes an optional fragments-directory argument and suppresses the CC subject bullet of any commit that itself added a fragment in the same range (`git log --diff-filter=A`), keyed on git commit identity rather than on a shared `#NNN` prose reference. This catches the ref-absent and ref-mismatched duplicates that `changelog_dedup_cc_by_fragment_refs` (which keys on the fragment filename id) structurally cannot, and it cannot silently drop genuinely-new content: a change with no fragment sits on a commit the suppression set never contains. The ref-based dedup is retained for the complementary separate-commit-same-ref case. Refs release-toolkit#493 (Bug 2). - `release-prep` no longer drops the `### Upgrade` section or concatenates a stray `None.` placeholder onto real content when composing a release over pre-existing `## [Unreleased]` content. `changelog_merge_sections` now sources its section order from the single-source-of-truth `CHANGELOG_STANDARD_SECTIONS` (so no hand-maintained order list can drift and drop a section) and treats the scaffold `None.` as a soft-empty sentinel that yields to real content but persists when a kind is empty in every input. Refs release-toolkit#493 (Bug 1). - **fragment-style**: scrub '[reviewer]' invented-jargon per register-check gate - **fragment-style**: scrub 3 chamber-name attributions per register-check gate ### Removed None. ### Deprecated None. ### Upgrade None.

release-bot force-pushed release-prep/rolling from dcbdbca64a to c58b31f952 2026-07-23 23:55:19 +02:00 Compare

release-bot force-pushed release-prep/rolling from c58b31f952 to af006f1a72 2026-07-24 00:02:38 +02:00 Compare

release-bot force-pushed release-prep/rolling from af006f1a72 to d2d9732bfa 2026-07-24 00:40:10 +02:00 Compare

release-bot force-pushed release-prep/rolling from d2d9732bfa to eb96b66ab4 2026-07-24 00:49:01 +02:00 Compare

release-bot force-pushed release-prep/rolling from eb96b66ab4 to f38267ec8f 2026-07-24 01:11:49 +02:00 Compare

alex approved these changes 2026-07-24 01:28:40 +02:00

alex merged commit f38267ec8f into main 2026-07-24 01:28:45 +02:00

alex deleted branch release-prep/rolling 2026-07-24 01:28:45 +02:00

Sign in to join this conversation.

Reviewers

No reviewers

alex

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

2 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!484

No description provided.