release-readiness: go/no-go for the next dotfiles-Windows release — 2026-07-16
Verdict: READY to cut v1.3.0 — meaningful feat work has accumulated past a patch, and auto-tag will never produce a minor on its own.
What would ship
The release's story is a host-tooling expansion — three feat(packages) waves from the awesome-windows sweep landed new host CLI commands that didn't exist before:
- Backup & media:
restic (the stack had no backup tool), yt-dlp, mpv
- CLI gap-fillers:
lsd, gsudo (in-session sudo), watchexec, trippy (trip), ast-grep (sg)
- Networking/sync + GUI:
syncthing, tailscale (pairs with the WSL bridge), ShareX, ollama
- A real
fix: the psmux prefix ? cheatsheet that rendered as 3 one-char columns (PowerShell array-flattening bug)
Mechanical churn already covered by auto-tag's patch tags: one sync nvim/starship from Core v3.6.0, a Windows Terminal settings tweak, and a docs: guide.
Proposed version + why → v1.3.0 (minor)
The bump is driven by the feat(packages) commits (#119/#120/#121) — new host commands are new capability, which is exactly a minor under the checklist (fix/chore/mirror-sync alone would be a patch auto-tag already handles). Nothing here is breaking — no removed/renamed module export or changed profile contract — so it stays a minor, not a major.
Tag-line drift: the last tag is v1.2.1 but the last deliberate ## [vX.Y.Z] heading is v1.2.0 — the tag line has run one mechanical patch ahead (the Core v3.6.0 nvim/starship sync earned the v1.2.1 auto-patch). The CHANGELOG's human-facing history is behind by that one patch.
Two small findings worth a glance while promoting:
[Unreleased] doesn't mention ollama, though commit db88489 added it — reconcile the entry.- The Windows Terminal settings change (875bdf3) isn't reflected in
[Unreleased] either.
Next step
Promote [Unreleased] under ## [v1.3.0] - 2026-07-16, folding in the missing ollama + Terminal-settings notes, then cut the v1.3.0 tag deliberately — auto-tag won't produce this minor on its own, and doing so reconciles the CHANGELOG heading past the drifted v1.2.1 tag.
Report only — I haven't edited CHANGELOG.md or tagged anything. You drive the release from here.
Filed by the claude-routines workflow. Report-first: review and act — nothing was changed.
release-readiness: go/no-go for the next dotfiles-Windows release — 2026-07-16
Verdict: READY to cut v1.3.0 — meaningful
featwork has accumulated past a patch, and auto-tag will never produce a minor on its own.What would ship
The release's story is a host-tooling expansion — three
feat(packages)waves from theawesome-windowssweep landed new host CLI commands that didn't exist before:restic(the stack had no backup tool),yt-dlp,mpvlsd,gsudo(in-session sudo),watchexec,trippy(trip),ast-grep(sg)syncthing,tailscale(pairs with the WSL bridge),ShareX,ollamafix: thepsmux prefix ?cheatsheet that rendered as 3 one-char columns (PowerShell array-flattening bug)Mechanical churn already covered by auto-tag's patch tags: one
sync nvim/starship from Core v3.6.0, a Windows Terminal settings tweak, and adocs:guide.Proposed version + why → v1.3.0 (minor)
The bump is driven by the
feat(packages)commits (#119/#120/#121) — new host commands are new capability, which is exactly a minor under the checklist (fix/chore/mirror-sync alone would be a patch auto-tag already handles). Nothing here is breaking — no removed/renamed module export or changed profile contract — so it stays a minor, not a major.Tag-line drift: the last tag is
v1.2.1but the last deliberate## [vX.Y.Z]heading isv1.2.0— the tag line has run one mechanical patch ahead (the Core v3.6.0 nvim/starship sync earned thev1.2.1auto-patch). The CHANGELOG's human-facing history is behind by that one patch.Two small findings worth a glance while promoting:
[Unreleased]doesn't mentionollama, though commit db88489 added it — reconcile the entry.[Unreleased]either.Next step
Promote
[Unreleased]under## [v1.3.0] - 2026-07-16, folding in the missingollama+ Terminal-settings notes, then cut thev1.3.0tag deliberately — auto-tag won't produce this minor on its own, and doing so reconciles the CHANGELOG heading past the driftedv1.2.1tag.Report only — I haven't edited
CHANGELOG.mdor tagged anything. You drive the release from here.Filed by the claude-routines workflow. Report-first: review and act — nothing was changed.