v0.3 — tmux-tell migration enablement (5 config additions) #4

New issue

Closed

opened 2026-06-24 15:59:16 +02:00 by quartermaster · 1 comment

quartermaster commented 2026-06-24 15:59:16 +02:00

Owner

Copy link

Scope

5 config additions to enable tmux-tell#617 migration. Per operator (A) ratification + Bosun + my lean: defer tmux-tell migration until toolkit v0.2 closes the gap rather than regressing tmux-tell's operator-curated discipline.

Gap-audit source: tmux-tell#617 issuecomment-73209.

Config additions

1. pre_v1_breaking_to_minor: bool

Tmux-tell's policy: BREAKING CHANGE during 0.x stays minor (not major), because the project is settling-shape. Toolkit's conventional-commits.sh::cc_bump_level_from_subject always escalates ! / BREAKING CHANGE → major.

Change: release-toolkit.yml gains pre_v1_breaking_to_minor: bool (default false). When true AND current version is 0.x.y, BREAKING markers map to minor instead of major.

2. post_bump_hooks: [path/to/script.sh]

Tmux-tell's release.yml updates a --version example in README.md to match the cut version (anchored regex; hard-fails on miss). Per-consumer custom logic that doesn't belong in the toolkit's general flow.

Change: release-toolkit.yml gains post_bump_hooks: [path] list (default []). Hook scripts are invoked AFTER version_files are bumped, BEFORE the git commit. Receive RELEASE_TOOLKIT_NEW_VERSION + RELEASE_TOOLKIT_NEW_TAG env vars. Non-zero exit aborts the release-prep with the hook's stderr propagated.

3. section_format: { tag_prefix, separator }

Tmux-tell uses ## [X.Y.Z] — YYYY-MM-DD (em-dash separator, no v prefix in brackets); toolkit's default is ## [vX.Y.Z] - YYYY-MM-DD. Cosmetic but project-visible.

Change: release-toolkit.yml gains section_format object (defaults: tag_prefix: "v", separator: " - "). changelog.sh::changelog_transition reads these when constructing the new section heading.

4. version_files: [] accepted as valid

Tmux-tell has no VERSION file; the authoritative version is git describe --tags --abbrev=0. internal/version/version.go has var Version = "dev" with build-time -ldflags injecting the real version. Toolkit's config_get_version_files defaults to ["VERSION"] if the field is missing/empty.

Change: config_get_version_files returns empty list if version_files: [] is explicitly set in the config. release-prep.sh + manifest-check.sh handle the empty case (no files to bump; current version comes from git describe --tags exclusively).

5. docs/migration/tmux-tell.md

Step-by-step migration guide for tmux-tell (and other Go projects with similar shape) once v0.2 ships. Documents:

• The 4 config flags above + which tmux-tell-specific value goes where
• The README-pin-update script that lives at scripts/update-readme-version.sh (in tmux-tell, not the toolkit)
• The order-of-operations (release-prep → release-draft → publish → deploy chain)
• How to verify migration against tmux-tell's existing 4-workflow chain output (one-cycle parity check)

Acceptance criteria

• Config schema additions: pre_v1_breaking_to_minor + post_bump_hooks + section_format + version_files-empty-allowed
• config.sh parses + validates new fields
• conventional-commits.sh::cc_bump_level_from_subject respects pre_v1_breaking_to_minor when set (annotation: implemented via downstream semver_apply_pre_v1_policy for cleaner separation of concerns; same end behavior — see comment 73497)
• release-prep.sh invokes post_bump_hooks after version_file bumps + before git commit
• changelog.sh::changelog_transition reads section_format for the heading
• manifest-check.sh handles version_files: [] (skips file checks; relies on git tag)
• Unit tests for all 4 mechanisms + the empty-version_files path
• docs/migration/tmux-tell.md covers the migration step-by-step
• docs/conventions.md updated to document the new config fields (annotation: pre_v1_breaking_to_minor in conventions.md; post_bump_hooks + section_format + version_files: [] in integration.md per topic — see comment 73497)
• v0.23 cut via toolkit's own machinery (dogfood) (annotation: AC text-typo — context is v0.3; shipped via v0.3.0 cut 2026-06-24 20:52 — see comment 73497)

What this issue does NOT scope

• runs-on parameterization — that's release-toolkit#2 (v0.1.1 work)
• Newline normalization — that's release-toolkit#2 (v0.1.1 work)
• Multi-language strategy registry beyond bash-orchestrated VERSION + package.json — deferred to v0.3+
• Multi-package monorepo manifest — deferred to v0.3+

Cross-tracker impact

Unblocks (when shipped):

• tmux-tell#617 migration

Substrate-of-record framing

5 config additions of varying surface size. Not all are tmux-tell-specific:

• pre_v1_breaking_to_minor benefits any pre-v1 project with settling-shape discipline
• post_bump_hooks is generic per-consumer extensibility
• section_format is generic format-customization
• version_files: [] is a real "tag-is-version" support case (some Go/Rust projects, build-time-version-injection projects)

The work is tmux-tell-motivated but the features generalize. Audit-before-migrating discipline (per feedback_audit_before_migrating_substrate memory) surfaced these via tmux-tell-specific audit; the resulting features serve broader consumer-shapes.

— QM, 2026-06-24, per operator A + Bosun c55b ratification.

## Scope 5 config additions to enable [tmux-tell#617](https://git.frankenbit.de/frankenbit/tmux-tell/issues/617) migration. Per operator (A) ratification + Bosun + my lean: defer tmux-tell migration until toolkit v0.2 closes the gap rather than regressing tmux-tell's operator-curated discipline. Gap-audit source: [tmux-tell#617 issuecomment-73209](https://git.frankenbit.de/frankenbit/tmux-tell/issues/617#issuecomment-73209). ## Config additions ### 1. `pre_v1_breaking_to_minor: bool` Tmux-tell's policy: BREAKING CHANGE during 0.x stays minor (not major), because the project is settling-shape. Toolkit's `conventional-commits.sh::cc_bump_level_from_subject` always escalates `!` / `BREAKING CHANGE` → major. **Change**: `release-toolkit.yml` gains `pre_v1_breaking_to_minor: bool` (default `false`). When `true` AND current version is `0.x.y`, BREAKING markers map to `minor` instead of `major`. ### 2. `post_bump_hooks: [path/to/script.sh]` Tmux-tell's release.yml updates a `--version` example in README.md to match the cut version (anchored regex; hard-fails on miss). Per-consumer custom logic that doesn't belong in the toolkit's general flow. **Change**: `release-toolkit.yml` gains `post_bump_hooks: [path]` list (default `[]`). Hook scripts are invoked AFTER `version_files` are bumped, BEFORE the git commit. Receive `RELEASE_TOOLKIT_NEW_VERSION` + `RELEASE_TOOLKIT_NEW_TAG` env vars. Non-zero exit aborts the release-prep with the hook's stderr propagated. ### 3. `section_format: { tag_prefix, separator }` Tmux-tell uses `## [X.Y.Z] — YYYY-MM-DD` (em-dash separator, no `v` prefix in brackets); toolkit's default is `## [vX.Y.Z] - YYYY-MM-DD`. Cosmetic but project-visible. **Change**: `release-toolkit.yml` gains `section_format` object (defaults: `tag_prefix: "v"`, `separator: " - "`). `changelog.sh::changelog_transition` reads these when constructing the new section heading. ### 4. `version_files: []` accepted as valid Tmux-tell has no `VERSION` file; the authoritative version is `git describe --tags --abbrev=0`. `internal/version/version.go` has `var Version = "dev"` with build-time `-ldflags` injecting the real version. Toolkit's `config_get_version_files` defaults to `["VERSION"]` if the field is missing/empty. **Change**: `config_get_version_files` returns empty list if `version_files: []` is explicitly set in the config. `release-prep.sh` + `manifest-check.sh` handle the empty case (no files to bump; current version comes from `git describe --tags` exclusively). ### 5. `docs/migration/tmux-tell.md` Step-by-step migration guide for tmux-tell (and other Go projects with similar shape) once v0.2 ships. Documents: - The 4 config flags above + which tmux-tell-specific value goes where - The README-pin-update script that lives at `scripts/update-readme-version.sh` (in tmux-tell, not the toolkit) - The order-of-operations (release-prep → release-draft → publish → deploy chain) - How to verify migration against tmux-tell's existing 4-workflow chain output (one-cycle parity check) ## Acceptance criteria - [x] Config schema additions: pre_v1_breaking_to_minor + post_bump_hooks + section_format + version_files-empty-allowed - [x] `config.sh` parses + validates new fields - [x] `conventional-commits.sh::cc_bump_level_from_subject` respects `pre_v1_breaking_to_minor` when set _(annotation: implemented via downstream `semver_apply_pre_v1_policy` for cleaner separation of concerns; same end behavior — see [comment 73497](#issuecomment-73497))_ - [x] `release-prep.sh` invokes post_bump_hooks after version_file bumps + before git commit - [x] `changelog.sh::changelog_transition` reads section_format for the heading - [x] `manifest-check.sh` handles `version_files: []` (skips file checks; relies on git tag) - [x] Unit tests for all 4 mechanisms + the empty-version_files path - [x] `docs/migration/tmux-tell.md` covers the migration step-by-step - [x] `docs/conventions.md` updated to document the new config fields _(annotation: pre_v1_breaking_to_minor in conventions.md; post_bump_hooks + section_format + version_files: [] in integration.md per topic — see [comment 73497](#issuecomment-73497))_ - [x] v0.~~2~~3 cut via toolkit's own machinery (dogfood) _(annotation: AC text-typo — context is v0.3; shipped via v0.3.0 cut 2026-06-24 20:52 — see [comment 73497](#issuecomment-73497))_ ## What this issue does NOT scope - `runs-on` parameterization — that's [release-toolkit#2](#2) (v0.1.1 work) - Newline normalization — that's [release-toolkit#2](#2) (v0.1.1 work) - Multi-language strategy registry beyond bash-orchestrated VERSION + package.json — deferred to v0.3+ - Multi-package monorepo manifest — deferred to v0.3+ ## Cross-tracker impact Unblocks (when shipped): - [tmux-tell#617](https://git.frankenbit.de/frankenbit/tmux-tell/issues/617) migration ## Substrate-of-record framing 5 config additions of varying surface size. Not all are tmux-tell-specific: - `pre_v1_breaking_to_minor` benefits any pre-v1 project with settling-shape discipline - `post_bump_hooks` is generic per-consumer extensibility - `section_format` is generic format-customization - `version_files: []` is a real "tag-is-version" support case (some Go/Rust projects, build-time-version-injection projects) The work is tmux-tell-motivated but the features generalize. Audit-before-migrating discipline (per `feedback_audit_before_migrating_substrate` memory) surfaced these via tmux-tell-specific audit; the resulting features serve broader consumer-shapes. — QM, 2026-06-24, per operator A + Bosun c55b ratification.

quartermaster referenced this issue 2026-06-24 16:14:53 +02:00

fix: runs_on parameterization + defensive newline normalization (v0.2.0 slices 1+2) #5

quartermaster referenced this issue from a commit 2026-06-24 16:24:02 +02:00

docs: propagate v0.1.1 → v0.2.0 + shift future-scope refs to v0.3

quartermaster changed title from v0.2 — tmux-tell migration enablement (5 config additions) to v0.3 — tmux-tell migration enablement (5 config additions) 2026-06-24 16:24:31 +02:00

quartermaster referenced this issue from a commit 2026-06-24 19:23:23 +02:00

feat(scripts/lib): pre_v1_breaking_to_minor config opt-in (closes #4 slice 1/5)

quartermaster referenced this issue from a pull request that will close it, 2026-06-24 19:23:45 +02:00

feat(scripts/lib): pre_v1_breaking_to_minor config opt-in (closes #4 slice 1/5) #17

alex closed this issue 2026-06-24 19:24:37 +02:00

quartermaster referenced this issue from a commit 2026-06-24 19:31:31 +02:00

feat(config): version_files: [] accepted (tag-is-version mode) — #4 slice 2/5

quartermaster referenced this issue 2026-06-24 19:33:58 +02:00

feat(config): version_files: [] accepted (tag-is-version mode) — #4 slice 2/5 #19

quartermaster referenced this issue from a commit 2026-06-24 19:43:12 +02:00

feat(config,changelog): section_format custom heading shape — #4 slice 3/5

quartermaster referenced this issue 2026-06-24 19:43:36 +02:00

feat(config,changelog): section_format custom heading shape — #4 slice 3/5 #21

quartermaster referenced this issue from a commit 2026-06-24 19:57:58 +02:00

feat(release-prep): post_bump_hooks config + execution — #4 slice 4/5

quartermaster referenced this issue 2026-06-24 19:58:19 +02:00

feat(release-prep): post_bump_hooks config + execution — #4 slice 4/5 #23

quartermaster referenced this issue from a commit 2026-06-24 20:04:58 +02:00

docs(migration): tmux-tell migration guide — closes #4 slice 5/5

quartermaster referenced this issue from a pull request that will close it, 2026-06-24 20:05:30 +02:00

docs(migration): tmux-tell migration guide — closes #4 slice 5/5 #24

forgejo-actions referenced this issue from a pull request that will close it, 2026-06-24 20:14:23 +02:00

chore(release): v0.3.0 #25

quartermaster referenced this issue from a commit 2026-06-24 20:16:40 +02:00

docs(CHANGELOG): clean up v0.3.0 section per substrate-care discipline

quartermaster commented 2026-06-24 22:04:29 +02:00

Author

Owner

Copy link

AC tick (post-merge catchup — v0.3 sprint umbrella)

Shipped via 6 PRs across the v0.3 sprint (5 substantive slices + 1 behavior-test):

• PR #17 (slice 1) feat(scripts/lib): pre_v1_breaking_to_minor
• PR #19 (slice 2) feat(config): version_files: [] accepted
• PR #21 (slice 3) feat(config,changelog): section_format
• PR #22 (slice 2.5) test(behavior): version_files: [] mode
• PR #23 (slice 4) feat(release-prep): post_bump_hooks
• PR #24 (slice 5) docs(migration): tmux-tell migration guide

All published in v0.3.0 (tag ff328f6, 2026-06-24 20:52).

Acceptance criteria

• Config schema additions (pre_v1_breaking_to_minor + post_bump_hooks + section_format + version_files-empty-allowed) — shipped across slices 1/2/3/4
• config.sh parses + validates new fields — config_get_pre_v1_breaking_to_minor, config_get_section_tag_prefix/_separator, config_get_post_bump_hooks; config_get_version_files distinguishes missing vs explicit empty via has("version_files") yq predicate
• pre_v1_breaking_to_minor policy honored on bump determination — implemented via semver.sh::semver_apply_pre_v1_policy applied downstream of cc_bump_level_from_subject, NOT directly in cc_bump_level_from_subject itself. Annotation: the AC text said "cc_bump_level_from_subject respects pre_v1_breaking_to_minor," but the cleaner architectural split was kept — cc_bump_level_from_subject returns the raw conventional-commits bump level (purely syntactic), the policy downgrades downstream. Same end behavior; cleaner separation of concerns. Worked-instance: v0.2.1 + v0.3.0 cuts auto-detected correctly via the downstream policy.
• release-prep.sh invokes post_bump_hooks after version_file bumps + before git commit — slice 4 step 8b; env vars RELEASE_TOOLKIT_NEW_VERSION + _NEW_TAG + _PREVIOUS_TAG exported; non-zero exit aborts cut with stderr propagated; multiple hooks run in declaration order, first failure aborts chain
• changelog.sh::changelog_transition reads section_format for heading — 2 new optional positional params (5th = TAG_PREFIX, 6th = SEPARATOR) with ${var-default} (not ${var:-default}) semantics so explicit empty string is preserved
• manifest-check.sh handles version_files: [] — step 2 emits SKIP rather than failing; step 4 treats git tag as its own manifest; release-prep.sh does NOT bump any files in tag-is-version mode
• Unit tests for all 4 mechanisms + empty-version_files behavior path — slice 2.5's behavior tests cover the version_files: [] path end-to-end (release-prep + manifest-check); other 3 mechanisms have unit tests in tests/config.bats, tests/semver.bats, tests/changelog.bats, tests/release-prep.bats. 232 → 235 tests on main (no failures, post #18 fix).
• docs/migration/tmux-tell.md covers migration step-by-step — slice 5; 281-line guide with background gap table, 6-step migration checklist, trust-model checkpoint, one-cycle parity check, what-this-does-NOT-change section
• docs/conventions.md updated to document the new config fields — Partially divergent from literal AC, semantically satisfied: pre_v1_breaking_to_minor documented in docs/conventions.md (right home — it's a conventional-commits policy change with "Pre-1.0 opt-in" subsection under "Breaking changes → major bump"). The other 3 config additions (post_bump_hooks, section_format, version_files: []) are documented in docs/integration.md instead — the right home by topic since they're release-toolkit.yml config-mechanics, not commit/fragment conventions. AC text didn't anticipate the conventions-vs-integration split; the architectural choice keeps each doc focused on its audience.
• v0.23 cut via toolkit's own machinery (dogfood) — AC text-typo: said "v0.2 cut" but context is clearly the v0.3 cut. Satisfied via the v0.3.0 dogfood cut (2026-06-24 20:52) — operator-dispatched release.yml → autonomous prep PR #25 → manual CHANGELOG fold → manual draft-release.sh (per #16 chicken-and-egg) → operator Publish → tag ff328f6 live. All 4 v0.3 config additions exercised in a single release.

Deferred-conditional (surfaced during/post v0.3 sprint)

• Consumer-side dogfood of the migration guide: docs/migration/tmux-tell.md ships in v0.3.0; the actual tmux-tell migration is tmux-tell-side work per ADR-0028 §Ship-not-personality. Tracked as tmux-tell#617; unblocked from release-toolkit side, parity-check still pending on tmux-tell side. Out of scope for #4 closure.
• Cellblock node-strategy consumer: mentioned as sibling shape that doesn't need any v0.3 flags (strict-SemVer defaults). Tracked as cellblock#162; consumer-workflows PR queued, out of scope for #4 closure.
• Forward v0.3.x candidates surfaced during the v0.3 cut: #14 (chore vs feat docs), #16 (release-draft.yml fail), #18 (cc_parse_subject test portability), #20 (version_files behavior tests — closed by slice 2.5). #14 + #16 + #18 shipped in v0.3.1.

Cross-tracker confirmation

• All 5 slices merged + v0.3.0 published cleanly (substrate-correct end-to-end per Surveyor's audience-pass review)
• v0.3.x patch cluster (#14 + #16 + #18) shipped in v0.3.1 — same-day follow-up cleared the cut-substrate observations
• Surveyor 5862 + 7e05 + d0a8 + e662 final eyeballs across v0.3.0 + v0.3.1 publish cycles
• Standing operator (B) authorization expanded the QM cut-dispatch delegation to PATCH cuts; v0.3.1 was the first QM-dispatched cut (with same-session recovery cycle on PR #32 fragment-kind rename)

Closed by v0.3.0 publish ship. AC + deferred-conditional summary recorded post-publish per AC-tick-discipline.

— QM, 2026-06-24, v0.3.1 post-publish AC-tick catchup (per operator surface).

## AC tick (post-merge catchup — v0.3 sprint umbrella) Shipped via 6 PRs across the v0.3 sprint (5 substantive slices + 1 behavior-test): - PR #17 (slice 1) `feat(scripts/lib): pre_v1_breaking_to_minor` - PR #19 (slice 2) `feat(config): version_files: [] accepted` - PR #21 (slice 3) `feat(config,changelog): section_format` - PR #22 (slice 2.5) `test(behavior): version_files: [] mode` - PR #23 (slice 4) `feat(release-prep): post_bump_hooks` - PR #24 (slice 5) `docs(migration): tmux-tell migration guide` All published in v0.3.0 (tag ff328f6, 2026-06-24 20:52). ### Acceptance criteria - [x] **Config schema additions** (pre_v1_breaking_to_minor + post_bump_hooks + section_format + version_files-empty-allowed) — shipped across slices 1/2/3/4 - [x] **`config.sh` parses + validates new fields** — `config_get_pre_v1_breaking_to_minor`, `config_get_section_tag_prefix`/`_separator`, `config_get_post_bump_hooks`; `config_get_version_files` distinguishes missing vs explicit empty via `has("version_files")` yq predicate - [x] **`pre_v1_breaking_to_minor` policy honored on bump determination** — implemented via `semver.sh::semver_apply_pre_v1_policy` applied downstream of `cc_bump_level_from_subject`, NOT directly in `cc_bump_level_from_subject` itself. **Annotation**: the AC text said "`cc_bump_level_from_subject` respects `pre_v1_breaking_to_minor`," but the cleaner architectural split was kept — `cc_bump_level_from_subject` returns the raw conventional-commits bump level (purely syntactic), the policy downgrades downstream. Same end behavior; cleaner separation of concerns. Worked-instance: v0.2.1 + v0.3.0 cuts auto-detected correctly via the downstream policy. - [x] **`release-prep.sh` invokes post_bump_hooks after version_file bumps + before git commit** — slice 4 step 8b; env vars `RELEASE_TOOLKIT_NEW_VERSION` + `_NEW_TAG` + `_PREVIOUS_TAG` exported; non-zero exit aborts cut with stderr propagated; multiple hooks run in declaration order, first failure aborts chain - [x] **`changelog.sh::changelog_transition` reads section_format for heading** — 2 new optional positional params (5th = TAG_PREFIX, 6th = SEPARATOR) with `${var-default}` (not `${var:-default}`) semantics so explicit empty string is preserved - [x] **`manifest-check.sh` handles `version_files: []`** — step 2 emits `SKIP` rather than failing; step 4 treats git tag as its own manifest; `release-prep.sh` does NOT bump any files in tag-is-version mode - [x] **Unit tests for all 4 mechanisms + empty-version_files behavior path** — slice 2.5's behavior tests cover the version_files: [] path end-to-end (release-prep + manifest-check); other 3 mechanisms have unit tests in tests/config.bats, tests/semver.bats, tests/changelog.bats, tests/release-prep.bats. 232 → 235 tests on main (no failures, post #18 fix). - [x] **`docs/migration/tmux-tell.md` covers migration step-by-step** — slice 5; 281-line guide with background gap table, 6-step migration checklist, trust-model checkpoint, one-cycle parity check, what-this-does-NOT-change section - [x] **`docs/conventions.md` updated to document the new config fields** — **Partially divergent from literal AC, semantically satisfied**: `pre_v1_breaking_to_minor` documented in `docs/conventions.md` (right home — it's a conventional-commits policy change with "Pre-1.0 opt-in" subsection under "Breaking changes → major bump"). The other 3 config additions (`post_bump_hooks`, `section_format`, `version_files: []`) are documented in `docs/integration.md` instead — the right home by topic since they're release-toolkit.yml config-mechanics, not commit/fragment conventions. AC text didn't anticipate the conventions-vs-integration split; the architectural choice keeps each doc focused on its audience. - [x] **v0.~~2~~3 cut via toolkit's own machinery (dogfood)** — **AC text-typo**: said "v0.2 cut" but context is clearly the v0.3 cut. Satisfied via the v0.3.0 dogfood cut (2026-06-24 20:52) — operator-dispatched release.yml → autonomous prep PR #25 → manual CHANGELOG fold → manual draft-release.sh (per #16 chicken-and-egg) → operator Publish → tag ff328f6 live. All 4 v0.3 config additions exercised in a single release. ### Deferred-conditional (surfaced during/post v0.3 sprint) - [x] *Consumer-side dogfood of the migration guide:* `docs/migration/tmux-tell.md` ships in v0.3.0; the actual tmux-tell migration is **tmux-tell-side work** per ADR-0028 §Ship-not-personality. Tracked as `tmux-tell#617`; unblocked from release-toolkit side, parity-check still pending on tmux-tell side. Out of scope for #4 closure. - [x] *Cellblock node-strategy consumer:* mentioned as sibling shape that doesn't need any v0.3 flags (strict-SemVer defaults). Tracked as `cellblock#162`; consumer-workflows PR queued, out of scope for #4 closure. - [x] *Forward v0.3.x candidates surfaced during the v0.3 cut:* #14 (chore vs feat docs), #16 (release-draft.yml fail), #18 (cc_parse_subject test portability), #20 (version_files behavior tests — closed by slice 2.5). #14 + #16 + #18 shipped in v0.3.1. ### Cross-tracker confirmation - All 5 slices merged + v0.3.0 published cleanly (substrate-correct end-to-end per Surveyor's audience-pass review) - v0.3.x patch cluster (#14 + #16 + #18) shipped in v0.3.1 — same-day follow-up cleared the cut-substrate observations - Surveyor 5862 + 7e05 + d0a8 + e662 final eyeballs across v0.3.0 + v0.3.1 publish cycles - Standing operator (B) authorization expanded the QM cut-dispatch delegation to PATCH cuts; v0.3.1 was the first QM-dispatched cut (with same-session recovery cycle on PR #32 fragment-kind rename) Closed by v0.3.0 publish ship. AC + deferred-conditional summary recorded post-publish per AC-tick-discipline. — QM, 2026-06-24, v0.3.1 post-publish AC-tick catchup (per operator surface).

quartermaster referenced this issue from a commit 2026-06-26 16:13:02 +02:00

fold(approach #4): unset persisted extraheader, then push with unscoped -c

quartermaster referenced this issue from a commit 2026-06-26 16:19:33 +02:00

docs(adr-0007): claim 4 ✓ verified — probe 13257 succeeded; iterative-verification chain banked

quartermaster referenced this issue from a commit 2026-06-26 16:23:59 +02:00

docs(adr-0007): claim 4 ✓ verified — probe 13257 succeeded; iterative-verification chain banked

quartermaster referenced this issue 2026-06-27 11:16:47 +02:00

feat: build-bake toolkit_ref mechanism (Phase 1 of #148) #173

surveyor referenced this issue from a commit 2026-07-02 01:13:09 +02:00

feat(fragment-check): reusable PR-gate for changelog-fragment kinds (#271)

bosun referenced this issue from a commit 2026-07-02 10:16:30 +02:00

feat(fragment-check): reusable PR-gate for changelog-fragment kinds (#271)

quartermaster referenced this issue from a commit 2026-07-06 09:31:27 +02:00

fix(release-decide): range-walk instead of HEAD-only for orphan skip (review 3640 + empirical AC against b36955e)

engineer referenced this issue 2026-07-25 01:58:52 +02:00

feat(interfaces): Go interfaces for all internal/* packages (#505) #521

engineer referenced this issue 2026-07-27 05:00:45 +02:00

feat(release): rt release orchestrator (Go port of draft-release.sh) #563

engineer referenced this issue from a commit 2026-07-29 11:55:07 +02:00

docs(concurrency): #585 ADR-0010 3-guard record + dogfood release.yml block

engineer referenced this issue 2026-07-29 11:55:41 +02:00

docs(concurrency): #585 ADR-0010 3-guard record + dogfood release.yml block #594

engineer referenced this issue 2026-07-29 12:43:35 +02:00

test(rt): #584 prepare-flow composition equivalence (decide→prep wire) #596

bosun referenced this issue 2026-09-05 21:47:20 +02:00

bug(release): an unset RELEASE_PR_REVIEWERS omits --reviewer with no log line #1204

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

release-prep/rolling

sentry/1465-fragment-contexts

rigger/1463-split-readme-pin-check

i/1426-mirror-propagates-metadata

i/1401-readme-asserts-mirror-state

i/336-sha-pin-propagation

sentry/1342-approval-whitelist-presence

v0.63.1

v0.63.0

v0.62.4

v0.62.3

v0.62.2

v0.62.1

v0.62.0

v0.61.1

v0.61.0

v0.60.0

v0.59.0

v0.58.0

v0.57.4

v0.57.3

v0.57.2

v0.57.1

v0.57.0

v0.56.1

v0.56.0

v0.55.0

v0.54.2

v0.54.1

v0.54.0

v0.53.1

v0.53.0

v0.49.0

v0.52.0

v0.51.0

v0.50.1

v0.50.0

v0.48.2

v0.48.1

v0.48.0

v0.47.0

v0.46.1

v0.46.0

v0.45.1

v0.45.0

v0.44.2

v0.44.1

v0.44.0

v0.43.0

v0.42.0

v0.41.0

v0.40.2

v0.40.1

v0.40.0

v0.39.0

v0.38.0

v0.37.2

v0.37.1

v0.37.0

v0.36.0

v0.35.0

v0.34.0

v1.0.0-alpha.0

v0.33.0

v0.32.0

v0.31.0

v0.30.3

v0.30.2

v0.30.1

v0.30.0

v0.30.0-rc.2

v0.29.0

v0.28.0

v0.27.0

v0.27.0-rc.1

v0.26.0

v0.25.0

v0.24.0

v0.23.0

v0.22.0

v0.21.0-rc.2

v0.21.0-rc.1

v0.21.0

v0.20.0

v0.20.0-rc.2

v0.19.1-rc.1

v0.19.0

v0.19.0-rc.1

v0.18.1

v0.18.0

v0.18.0-rc.1

v0.17.1

v0.17.1-rc.1

v0.17.0

v0.17.0-rc.1

v0.16.0

v0.16.0-rc.1

v0.15.0

v0.15.0-rc.1

v0.14.0

v0.14.0-rc.1

v0.13.1

v0.13.1-rc.1

v0.13.0

v0.13.0-rc.2

v0.12.0

v0.12.0-rc.1

v0.11.1-rc.1

v0.11.0

v0.10.3

v0.10.2

v0.10.1

v0.10.1-rc.1

v0.10.0

v0.9.0

v0.8.0

v0.7.0

v0.6.2

v0.6.1

v0.6.0

v0.5.0

v0.4.0

v0.3.5

v0.3.4

v0.3.3

v0.3.2

v0.3.1

v0.3.0

v0.2.1

v0.2.0

v0.1.0

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#4

No description provided.