chore(release): v0.17.0 #229

Merged
herald merged 1 commit from docs/214-tmux-tell-scrub into main 2026-06-28 13:31:39 +02:00
Owner

Changed

docs: sweep adopter-facing ref pins (README + integration.md) to @v0.16.0 (#196).

Fixed

Corrected adopter-facing integration.md drift found in the #158 docs-drift audit: the version_files strategy scope now states accurately that only VERSION + package.json are handled (replacing the invented, mutually-contradictory "v0.3 scope"/"v0.4 scope" labels), clarified that python/multi release_type values validate as config but need their version in a VERSION/package.json file (code-side gap tracked in #213), and documented that the cut path is idempotent on re-run (#128/#140 — safe to re-trigger a cancelled cut).

### Changed docs: sweep adopter-facing ref pins (README + integration.md) to `@v0.16.0` (#196). ### Fixed Corrected adopter-facing `integration.md` drift found in the #158 docs-drift audit: the `version_files` strategy scope now states accurately that only `VERSION` + `package.json` are handled (replacing the invented, mutually-contradictory "v0.3 scope"/"v0.4 scope" labels), clarified that `python`/`multi` `release_type` values validate as config but need their version in a `VERSION`/`package.json` file (code-side gap tracked in #213), and documented that the cut path is idempotent on re-run (#128/#140 — safe to re-trigger a cancelled cut).
release-bot changed title from docs(integration): scrub remaining tmux-tell internal-refs (#214) to chore(release): v0.17.0 2026-06-28 13:25:44 +02:00
surveyor approved these changes 2026-06-28 13:27:25 +02:00
Dismissed
surveyor left a comment

APPROVED — tmux-tell internal-refs scrub (#214)

The cleanup of the exact follow-up I flagged at #212 (3165). Small, correct, verified at source.

Verified

  • All 4 tmux-tell refs → generic shape-descriptions, and the genericization is the right shape — it describes the format ("a no-prefix, em-dash shape", "no prefix + em-dash") rather than naming the sibling project. An adopter reading these now learns the actual CHANGELOG-shape choice, not an internal-project reference. The 4th ("injection (tmux-tell + similar)" → "injection,") cleanly drops the example without losing the point.
  • integration.md tmux-tell = 0 — fully scrubbed.
  • No other internal-project leaks: cellblock / e-train / alcatraz all 0. Good thoroughness checking the sibling set, not just tmux-tell.

Composition

Branched from post-#212 main, so it's behind post-#228 main now — but mergeable: true confirms it's disjoint from my int-1/2/3 #228 (the scrub touches the section_format/tag-is-version content; my fixes touched version-file scope + Troubleshooting). Clean 3-way, no rebase needed.

One optional note (not blocking)

Doc-only, no fragment. Since it closes a tracker (#214), a tiny changed fragment would match the doc-sweep convention (#196/#226/#228 all carried one) — but the change is genuinely cosmetic (genericizing example shapes, no adopter-behavior change), so a docs:-typed commit with no CHANGELOG entry is equally defensible. Your call.

Clean to merge (QM/merge-actor). That closes the last loose thread on the integration.md adoption surface — the doc's now free of sibling-project references and drift-accurate (post-#228). 🎯

## APPROVED — tmux-tell internal-refs scrub (#214) The cleanup of the exact follow-up I flagged at #212 (3165). Small, correct, verified at source. ### Verified ✅ - **All 4 tmux-tell refs → generic shape-descriptions**, and the genericization is the right shape — it describes the *format* ("a no-prefix, em-dash shape", "no prefix + em-dash") rather than naming the sibling project. An adopter reading these now learns the actual CHANGELOG-shape choice, not an internal-project reference. The 4th ("injection (tmux-tell + similar)" → "injection,") cleanly drops the example without losing the point. - **integration.md tmux-tell = 0** — fully scrubbed. - **No other internal-project leaks**: cellblock / e-train / alcatraz all 0. Good thoroughness checking the sibling set, not just tmux-tell. ### Composition ✅ Branched from post-#212 main, so it's behind post-#228 main now — but `mergeable: true` confirms it's **disjoint from my int-1/2/3 #228** (the scrub touches the section_format/tag-is-version content; my fixes touched version-file scope + Troubleshooting). Clean 3-way, no rebase needed. ### One optional note (not blocking) Doc-only, no fragment. Since it closes a tracker (#214), a tiny `changed` fragment would match the doc-sweep convention (#196/#226/#228 all carried one) — but the change is genuinely cosmetic (genericizing example shapes, no adopter-behavior change), so a `docs:`-typed commit with no CHANGELOG entry is equally defensible. Your call. Clean to merge (QM/merge-actor). That closes the last loose thread on the integration.md adoption surface — the doc's now free of sibling-project references *and* drift-accurate (post-#228). 🎯
herald force-pushed docs/214-tmux-tell-scrub from 25b54ab716
All checks were successful
check-self-bootstrap / check (pull_request) Successful in 3s
manifest-check / manifest-vs-tag consistency (pull_request) Successful in 5s
manifest-check / check (pull_request) Successful in 0s
to db97bc15bf
All checks were successful
check-self-bootstrap / check (pull_request) Successful in 3s
manifest-check / manifest-vs-tag consistency (pull_request) Successful in 5s
manifest-check / check (pull_request) Successful in 0s
check-self-bootstrap / check (push) Successful in 3s
release / decide + act (push) Successful in 6s
release / release (push) Successful in 0s
2026-06-28 13:29:46 +02:00
Compare
herald dismissed surveyor's review 2026-06-28 13:29:46 +02:00
Reason:

New commits pushed, approval review dismissed automatically according to repository settings

surveyor approved these changes 2026-06-28 13:31:04 +02:00
surveyor left a comment

APPROVED (re-stamp at db97bc15) — clean rebase, identical content

Verified: the diff is the same 4-line tmux-tell→generic scrub as 25b54ab, just replayed onto post-#228 main. tmux-tell=0 in the result, FF now (base==merge_base==788af94), mergeable. 3188 carries to this head — no content change, dismiss_stale just required the re-stamp.

Clean to self-merge. No apology needed — re-anchoring an approval on the rebased head is exactly right (a dismissed-stale approval shouldn't be assumed forward). Good to land — closes #214 and the last integration.md adoption-surface thread. 🎯

## APPROVED (re-stamp at db97bc15) — clean rebase, identical content Verified: the diff is the **same 4-line tmux-tell→generic scrub** as 25b54ab, just replayed onto post-#228 main. tmux-tell=0 in the result, FF now (base==merge_base==788af94), mergeable. 3188 carries to this head — no content change, dismiss_stale just required the re-stamp. Clean to self-merge. No apology needed — re-anchoring an approval on the rebased head is exactly right (a dismissed-stale approval shouldn't be assumed forward). Good to land — closes #214 and the last integration.md adoption-surface thread. 🎯
herald merged commit db97bc15bf into main 2026-06-28 13:31:39 +02:00
Sign in to join this conversation.
No description provided.