Skip to content

ci: release with chant release - #73

Merged
lex00 merged 2 commits into
mainfrom
chant-release
Nov 17, 2026
Merged

lex00 merged 2 commits into
mainfrom
chant-release

Conversation

@lex00

@lex00 lex00 commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

Closes #72

Releases move to chant release (chant 0.124.103, run with a pinned npx; chant is not a dependency). .github/workflows/release.yml keeps its name and is now generated by chant release workflow from chant.config.json; it is started by hand (just release X.Y.Z, or gh workflow run release.yml -f label=auto), cuts the newest green commit of main, pushes vX.Y.Z and publishes.

What the old release produced, and where it lands now:

Before (goreleaser release --clean on a v* tag) Now
Binaries for linux/darwin/windows x amd64/arm64, mudflaps_X.Y.Z_<os>_<arch>.tar.gz (.zip on windows) with README, LICENSE, CHANGELOG Same goreleaser builds and archives, run at the cut as goreleaser release --snapshot with snapshot.version_template: "{{ .Env.CHANT_RELEASE_LABEL }}"; recorded by digest as artifact:goreleaser
checksums.txt Same file, same artifact
GitHub Release vX.Y.Z forge target on INTENTIUS/mudflaps, tag v{version}; the existing v* tags are read as history (legacyTags)
Release notes: commits since the previous tag minus docs:/test:/chore: notes.generate: "commits" with every conventional type except those three; non-conventional subjects are no longer listed (INTENTIUS/chant#5270)
ghcr.io/intentius/mudflaps:X.Y.Z and :latest, linux/amd64 + linux/arm64, VERSION build-arg, OCI source/version/licenses labels release.images entry building the top-level Dockerfile for both platforms, reproducibly, with the same build-arg and labels; oci target with tags {label} and latest
:X.Y.Z-amd64 / :X.Y.Z-arm64 per-arch tags Not published; the oci target can't tag per-platform manifests and no doc names them (INTENTIUS/chant#5269)

No SBOMs or signatures existed before, and none are added. dockers, docker_manifests and changelog leave .goreleaser.yaml, since chant builds the image and writes the notes. Dockerfile.goreleaser is no longer used and is left in place. The image archive is written to out/ (ignored) because goreleaser's --clean empties dist/.

RELEASING.md, CONTRIBUTING.md, and the just release / make release recipes describe the new flow; the recipes keep their preflight (clean main, CHANGELOG section, build/vet/gofmt/test) and dispatch the workflow instead of pushing a tag.

Checks run locally:

  • go build, go vet, gofmt -l, go test ./..., golangci-lint run: pass.
  • goreleaser release --snapshot --clean --skip=publish (goreleaser 2.17.0) with CHANT_RELEASE_LABEL=0.5.1: the same six archives and checksums.txt as v0.5.0's release, binary reports version=0.5.1.
  • chant release next: 0.5.1, patch from the tag v0.5.0.
  • chant release cut auto --dry-run in a scratch clone: refused with release-commit-not-green because this commit has no checks yet. With green: "none" in the scratch clone only, the dry run built the multi-arch image archive and the goreleaser files and planned both targets.
  • chant release doctor: forge token and access ok; GHCR credentials can't be checked from a workstation (the job gets OCI_USERNAME/OCI_PASSWORD from github.token).
  • chant audit . --fail-on merge-worthy: the generated release.yml has two merge-worthy findings, GHA049 and SEC010, from chant's generator (release workflow: the generated file fails chant audit with goreleaser artifacts and images (GHA049, SEC010), and sets up Go twice chant#5268). The other findings are in the existing ci.yml and docs.yml.

@lex00
lex00 enabled auto-merge November 17, 2026 21:37
@lex00
lex00 added this pull request to the merge queue Nov 17, 2026
Merged via the queue into main with commit 4fdb554 Nov 17, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

release: publish through chant release

1 participant