ci(release): ignore buildkitd.toml dropped by Blacksmith builder

useblacksmith/setup-docker-builder drops a buildkitd.toml in the repo
root when it initialises buildx. goreleaser's dirty-state check then
refuses to proceed, which is why v2.5.0 and v2.6.0 shipped without any
release artifacts.

.gitignore excludes the file for new commits. The release workflow also
writes it to .git/info/exclude after the builder step so that backfill
dispatches against historical tags (whose .gitignore predates this
commit) still see a clean working tree.

Author: cpcloud

.github/workflows/release.yml

@@ -53,6 +53,13 @@ jobs:
       - name: Setup Blacksmith Builder
         uses: useblacksmith/setup-docker-builder@ac083cc84672d01c60d5e8561d0a939b697de542 # v1
 
+      # The Blacksmith builder drops buildkitd.toml in the repo root. The
+      # repo's .gitignore excludes it on main, but historical tags predate
+      # that entry, so ignore it per-run to keep goreleaser's dirty-state
+      # check happy on backfills too.
+      - name: Ignore buildkitd.toml locally
+        run: echo buildkitd.toml >> .git/info/exclude
+
       - uses: docker/login-action@4907a6ddec9925e35a0a9e82d7399ccc52663121 # v4.1.0
         with:
           registry: ${{ env.REGISTRY }}

.gitignore

@@ -41,6 +41,9 @@ vendor
 # GoReleaser
 dist/
 
+# Dropped by useblacksmith/setup-docker-builder in CI
+buildkitd.toml
+
 # Nix
 .direnv
 result