From 673bdc1dc4ee6442a87bbeca66f7c5fd47a15886 Mon Sep 17 00:00:00 2001 From: Guillaume Date: Sun, 6 Sep 2026 00:37:07 +0200 Subject: [PATCH] fix(ci): note incompatibility with GitHub immutable releases Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01Y1zVUQDr4rhZozGUQBgHgH --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index 68f6f9c..218aeec 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -41,6 +41,7 @@ e2e/ - `release-please` (release-type `go`) runs on every push to `main`, maintaining a Release PR with `CHANGELOG.md` and the next version bump computed from commit history - Commits and PR titles must follow Conventional Commits (`feat:`, `fix:`, `chore:`, …) — release-please can't decide a bump or write the changelog otherwise - Merging the Release PR tags the release and creates the GitHub Release; a second job in the same workflow (`.github/workflows/release-please.yaml`), gated on `release_created`, then builds and attaches binaries via `goreleaser` (`.goreleaser.yaml`) — a tag-push-triggered workflow wouldn't fire here, since GitHub doesn't cascade a new run from a ref created by the workflow's own `GITHUB_TOKEN` +- FYI: this release pipeline is incompatible with GitHub's "immutable releases" setting — keep it disabled ## Key conventions