~bigbes/ci-cacher: publish.yml: goreleaser --skip=validate

d44d75de0f007b7a1d4f4fade402fe10653413f9 — Eugene Blikh 2 days ago 462e616

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).

patch browse .tar.gz

1 files changed, 6 insertions(+), 1 deletions(-)

M .builds/publish.yml

M .builds/publish.yml => .builds/publish.yml +6 -1

@@ 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.