fix(release): ignore BuildKit configs written into the checkout - #25
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.