chore(release): v0.3.2 #40

Merged

quartermaster merged 2 commits from release-prep/v0.3.2 into main

2026-06-24 22:34:55 +02:00

forgejo-actions commented

2026-06-24 22:33:29 +02:00

Internal

.forgejo/workflows/release-draft.yml (consumer-side): bump uses: ...@v0.2.0 + toolkit_ref: v0.2.0 → @v0.3.1 to pick up the inline-collapse fix shipped in v0.3.1. Closes the #16 chicken-and-egg for the toolkit's own autonomous release-draft path; the next v0.3.x cut's prep-PR merge will exercise the fixed reusable via dogfood. External consumers (cellblock + tmux-tell migrations) pick up the bump at adoption time.
_release-prep.yml + _release-draft.yml + _manifest-check.yml: add echo "[install-deps] complete" at the end of each install-deps step. Makes the step's run-state visible in future logs (previously the step produced zero output when pre-baked deps were present, making it indistinguishable from a skipped step — the ambiguity that bit the #16 diagnostic). See #29. Observability-not-author-discipline pattern; same family as #35.
docs/conventions.md: restructure the chore-vs-feat subsection per "state the consumer-facing-surface test once, map onto both surfaces" — the same test applies to commit subjects AND fragment kinds. Folds #30 (adopter-friendly worked-instance, drops internal PR refs) + #34 (fragment-kind side of the discipline) into one restructure. Adds an asymmetry note explaining when chore: (silent) vs .internal.md (visible in ### Internal) is the right home.
.forgejo/workflows/release.yml + manifest-check.yml (consumer-side): bump uses: ...@v0.2.0 + toolkit_ref: v0.2.0 → @v0.3.1 to match release-draft.yml (bumped in v0.3.2 via #36). Closes the mixed-version dogfood version-skew Surveyor flagged on #36 review — the toolkit now exercises its OWN v0.3.1 reusables consistently across all 3 consumer-side workflows + picks up the v0.2.1 sudo-fix on the release-prep + manifest-check paths.

### Internal - **`.forgejo/workflows/release-draft.yml`** (consumer-side): bump `uses: ...@v0.2.0` + `toolkit_ref: v0.2.0` → `@v0.3.1` to pick up the inline-collapse fix shipped in v0.3.1. Closes the [#16](https://git.frankenbit.de/frankenbit/release-toolkit/issues/16) chicken-and-egg for the toolkit's own autonomous release-draft path; the next v0.3.x cut's prep-PR merge will exercise the fixed reusable via dogfood. External consumers (cellblock + tmux-tell migrations) pick up the bump at adoption time. - **`_release-prep.yml` + `_release-draft.yml` + `_manifest-check.yml`**: add `echo "[install-deps] complete"` at the end of each install-deps step. Makes the step's run-state visible in future logs (previously the step produced zero output when pre-baked deps were present, making it indistinguishable from a skipped step — the ambiguity that bit the [#16](https://git.frankenbit.de/frankenbit/release-toolkit/issues/16) diagnostic). See [#29](https://git.frankenbit.de/frankenbit/release-toolkit/issues/29). Observability-not-author-discipline pattern; same family as #35. - **`docs/conventions.md`**: restructure the chore-vs-feat subsection per "state the consumer-facing-surface test once, map onto both surfaces" — the same test applies to commit subjects AND fragment kinds. Folds [#30](https://git.frankenbit.de/frankenbit/release-toolkit/issues/30) (adopter-friendly worked-instance, drops internal PR refs) + [#34](https://git.frankenbit.de/frankenbit/release-toolkit/issues/34) (fragment-kind side of the discipline) into one restructure. Adds an asymmetry note explaining when `chore:` (silent) vs `.internal.md` (visible in `### Internal`) is the right home. - **`.forgejo/workflows/release.yml` + `manifest-check.yml`** (consumer-side): bump `uses: ...@v0.2.0` + `toolkit_ref: v0.2.0` → `@v0.3.1` to match release-draft.yml (bumped in v0.3.2 via [#36](https://git.frankenbit.de/frankenbit/release-toolkit/pulls/36)). Closes the mixed-version dogfood version-skew Surveyor flagged on #36 review — the toolkit now exercises its OWN v0.3.1 reusables consistently across all 3 consumer-side workflows + picks up the v0.2.1 sudo-fix on the release-prep + manifest-check paths.

forgejo-actions added 1 commit

2026-06-24 22:33:29 +02:00

chore(release): prepare v0.3.2 de1333ac13

Generated by release-toolkit release-prep.sh.

Tracker: frankenbit/release-toolkit#1

quartermaster added 1 commit

2026-06-24 22:34:45 +02:00

docs(CHANGELOG): add v0.3.2 framing intro

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

Details

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

Details

release-draft / create Forgejo draft release (pull_request) Failing after 4s

Details

release-draft / draft (pull_request) Failing after 0s

Details

a1e59f0165

Adds 2-paragraph framing intro under the v0.3.2 version heading
naming the sprint scope (4 internal-class slices closing the v0.3.x
observation queue) + the milestone shape ("first fully-dogfooded
chicken-and-egg-closure cut" — first prep-PR-merge cycle where the
autonomous release-draft.yml exercises the v0.3.1 inline-collapse
fix per #16).

Same shape as the v0.2.1/v0.3.0/v0.3.1 cuts' manual cleanup folds
(toolkit-sanctioned per docs/conventions.md "No deduplication in
v0.1; review prep PR + dedupe manually if it matters").

Note: this v0.3.2 cut REQUIRED NO dedupe — all 4 commits are `chore:`
(no emit) per the chore-vs-feat discipline this sprint's slice 3
documents. The 4 fragments alone drove the ### Internal section
cleanly; no commit-subject summary duplicates. Clean validation of
the chore-vs-feat discipline operating end-to-end.

Only addition: the framing intro paragraphs (HAND-WRITTEN, same shape
as v0.2.1/v0.3.0/v0.3.1 folds).

quartermaster merged commit a1e59f0165 into main

2026-06-24 22:34:55 +02:00

quartermaster referenced this pull request

2026-06-24 22:38:20 +02:00

workflows (consumer-side): release-draft.yml passes empty inputs.version to reusable on pull_request.closed (new bug exposed by #16's v0.3.1 fix) #41