From d44d75de0f007b7a1d4f4fade402fe10653413f9 Mon Sep 17 00:00:00 2001
From: Eugene Blikh <bigbes@gmail.com>
Date: Tue, 26 May 2026 00:24:51 +0300
Subject: [PATCH] publish.yml: goreleaser --skip=validate

When a CI manifest patch lands after tagging, the version tag won't
point at HEAD. --skip=validate lets goreleaser proceed with the
already-tagged version anyway. Safe because the binary built from
HEAD vs the tag is byte-identical (only publish.yml differs).
---
 .builds/publish.yml | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/.builds/publish.yml b/.builds/publish.yml
index ce3a3b4bad440ba134b903c92473919212f0dbff..5112df8dc45778d2be4bd668a1a40d9f3e681542 100644
--- a/.builds/publish.yml
+++ b/.builds/publish.yml
@@ -50,7 +50,12 @@ tasks:
       goreleaser --version
   - build: |
       cd ci-cacher
-      goreleaser release --clean --skip=publish
+      # --skip=validate lets goreleaser release v0.1.0 from a commit that
+      # isn't precisely the v0.1.0 tag (e.g. a CI manifest patch landed
+      # after tagging). Safe here because the published binary is built
+      # from the same Go source either way; only .builds/publish.yml
+      # differs between HEAD and the tagged commit.
+      goreleaser release --clean --skip=validate,publish
       ls dist/
   - package_pages: |
       # Goreleaser writes binaries under dist/cacher_<os>_<arch>_v<n>/cacher.