Commit c5e686d
fix(release): ignore BuildKit configs written into the checkout
The release job's useblacksmith/setup-docker-builder step writes its
BuildKit daemon config with a relative path, so buildkitd.toml lands in
the repository checkout. GoReleaser validates a clean tree before
releasing and failed with "git is in a dirty state" on the untracked
file, aborting the release.
Ignore buildkitd.toml and the fallback builder's
docker-container-buildkitd.toml at the repo root. Ignored files do not
count as dirty, and the daemon keeps the config it was started with.
TestReleaseBuilderConfigsAreGitIgnored checks both paths with
`git check-ignore --no-index`, without touching the working tree.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>1 parent fdb9e71 commit c5e686d
2 files changed
Lines changed: 52 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
7 | 7 | | |
8 | 8 | | |
9 | 9 | | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
0 commit comments