Skip to content

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

Merged
cpcloud merged 1 commit intomicasa-dev:mainfrom
cpcloud:fix/release-buildkitd-toml
Apr 18, 2026
Merged

ci(release): ignore buildkitd.toml dropped by Blacksmith builder#955
cpcloud merged 1 commit intomicasa-dev:mainfrom
cpcloud:fix/release-buildkitd-toml

Conversation

@cpcloud
Copy link
Copy Markdown
Collaborator

@cpcloud cpcloud commented Apr 18, 2026

Summary

  • useblacksmith/setup-docker-builder drops buildkitd.toml in the repo
    root, which trips goreleaser's dirty-state check. v2.5.0 and v2.6.0
    shipped with no release artifacts for this reason.
  • Adds a workflow step after the builder setup that writes the file's
    name to .git/info/exclude, so both release:published runs and
    workflow_dispatch backfills of older tags see a clean working tree.

@cpcloud cpcloud added bug Something isn't working ci CI/CD pipeline changes labels Apr 18, 2026
useblacksmith/setup-docker-builder drops a buildkitd.toml in the repo
root, which trips goreleaser's dirty-state check. Exclude the file via
.git/info/exclude before goreleaser runs so that release:published
builds and workflow_dispatch backfills of older tags both see a clean
working tree.

v2.5.0 and v2.6.0 shipped without release artifacts because of this.
@cpcloud cpcloud force-pushed the fix/release-buildkitd-toml branch from 422261e to 8c17152 Compare April 18, 2026 11:50
@cpcloud cpcloud enabled auto-merge (squash) April 18, 2026 11:51
@cpcloud cpcloud merged commit 8a5e33a into micasa-dev:main Apr 18, 2026
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working ci CI/CD pipeline changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant