ci: migrate release automation to release-please (Phase 1)#127
Merged
Conversation
Implements the release-please flow from ADR-0002 and the Phase 1 P0 tag subset from ADR-0003, reworking the in-flight Semantic Release draft (#107) into release-please. - add release-please-config.json (simple release type, v-prefixed tags) - add .release-please-manifest.json seeded at 8.0.0 to continue the existing major line under project semver (vX.Y.Z) - add .github/workflows/release-please.yml — maintains the Release PR and creates the GitHub release + version tag on merge - migrate .github/workflows/release.yml to trigger on the vX.Y.Z tag and publish the Phase 1 tag subset: fully-pinned vX.Y.Z_tf-A.B.C_aws-D.E.F (every combination) plus vX.Y.Z and latest on the latest bundled combination; the manual release trigger is removed Out of scope (Phase 3): edge / floating vX.Y tags, GHCR, the zenika->bgauduch rename and docker/login-action migration. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YDmRomapTbonHPFwnU61zR
Switch to a single release-please.yml workflow: the image build/push matrix runs in the same workflow, gated on the release-please `release_created` output. This drops the separate tag-triggered release.yml and removes the need for a Personal Access Token (tags pushed by GITHUB_TOKEN do not trigger other workflows), fitting the low-friction driver of ADR-0002. - combine build/push (Phase 1 P0 tags from ADR-0003) into release-please.yml - delete .github/workflows/release.yml - README: point the release badge to release-please.yml - roadmap + ADR-0002: amend the mechanism wording (decision unchanged) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YDmRomapTbonHPFwnU61zR
Verified against the release-please-action docs: - root-component outputs are NOT path-prefixed; use steps.release.outputs.release_created / tag_name (the prior ".--"-prefixed form would have been empty, so build/push never ran) - add bootstrap-sha (8.0 release commit) so the first managed release only rolls up commits since the last published release instead of the whole history; manifest stays seeded at the current version (8.0.0) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YDmRomapTbonHPFwnU61zR
This was referenced Jun 25, 2026
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
2 participants
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.
Implements the release-please flow from ADR-0002 and the Phase 1 P0
tag subset from ADR-0003, reworking the in-flight Semantic Release
draft (#107) into release-please.
existing major line under project semver (vX.Y.Z)
and creates the GitHub release + version tag on merge
and publish the Phase 1 tag subset: fully-pinned
vX.Y.Z_tf-A.B.C_aws-D.E.F (every combination) plus vX.Y.Z and latest
on the latest bundled combination; the manual release trigger is removed
Out of scope (Phase 3): edge / floating vX.Y tags, GHCR, the
zenika->bgauduch rename and docker/login-action migration.
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01YDmRomapTbonHPFwnU61zR