From 9ceddd39c1dca1f1ed505fb32ae1d7fb5519c8d7 Mon Sep 17 00:00:00 2001 From: vikingowl Date: Fri, 22 May 2026 13:06:24 +0200 Subject: [PATCH] chore(todo): track dockers_v2 migration under distribution follow-ups GoReleaser is phasing out the dockers + docker_manifests pair in favour of dockers_v2, which collapses our four-block setup into one. The migration also touches Dockerfile (per-platform binary layout in the build context), so it's worth scheduling as its own commit rather than a release-time rush. --- TODO.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/TODO.md b/TODO.md index 6b651a9..a9f8ac6 100644 --- a/TODO.md +++ b/TODO.md @@ -34,7 +34,11 @@ Active work, newest first. `curl | sh` installer script, signed checksums (cosign/sigstore), release note automation, Windows process-tree kill via golang.org/x/sys/windows job objects (currently `os.Process.Kill` - only — see `internal/mcp/transport_windows.go`). + only — see `internal/mcp/transport_windows.go`), and migration + from `dockers` + `docker_manifests` to `dockers_v2` in + `.goreleaser.yml` (collapses ~45 lines into one block but + requires Dockerfile changes for the per-platform binary layout + — deferred to its own commit before v0.3.0). ## Stable backlog (not in active phases)