chore(release): v0.17.0 #229
No reviewers
Labels
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
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/release-toolkit!229
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/214-tmux-tell-scrub"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Changed
docs: sweep adopter-facing ref pins (README + integration.md) to
@v0.16.0(#196).Fixed
Corrected adopter-facing
integration.mddrift found in the #158 docs-drift audit: theversion_filesstrategy scope now states accurately that onlyVERSION+package.jsonare handled (replacing the invented, mutually-contradictory "v0.3 scope"/"v0.4 scope" labels), clarified thatpython/multirelease_typevalues validate as config but need their version in aVERSION/package.jsonfile (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).docs(integration): scrub remaining tmux-tell internal-refs (#214)to chore(release): v0.17.0APPROVED — tmux-tell internal-refs scrub (#214)
The cleanup of the exact follow-up I flagged at #212 (3165). Small, correct, verified at source.
Verified ✅
Composition ✅
Branched from post-#212 main, so it's behind post-#228 main now — but
mergeable: trueconfirms 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
changedfragment 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 adocs:-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). 🎯
25b54ab716db97bc15bfNew commits pushed, approval review dismissed automatically according to repository settings
APPROVED (re-stamp at
db97bc15) — clean rebase, identical contentVerified: 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. 🎯