ci: adopt release-please for commit-driven versioning - #34
Merged
Conversation
Replace the manual bump-version + changelog-fragment flow with release-please:
- release-please-config.json + .release-please-manifest.json (single package ".",
version tracked and stamped into go/cmd/root.go via an x-release-please-version
marker); tag format vX.Y.Z.
- release-please.yml opens/maintains the release PR on push to main and, when a
release is cut, calls release.yml to build + attach the binaries (avoids the
GITHUB_TOKEN tag-does-not-trigger-workflows trap).
- release.yml is now also a reusable workflow (workflow_call tag input) and
creates-or-uploads the release via gh.
- pr-title.yml enforces Conventional Commit PR titles (squash-merge -> release
commit that release-please reads).
- Remove scripts/{bump-version,new-change,render-changelog} and .changes/;
update CODEOWNERS, CONTRIBUTING, CLAUDE.md, docs/development, PR template.
This was referenced Jul 7, 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
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.
Summary
Item #6 of the CLI-flow alignment: replace the manual
bump-version+ changelog-fragment process with release-please (commit-driven versioning + CHANGELOG), matching the greennode-mcp flow. Also adds the Conventional Commits PR-title gate (item #3's title part), which is now meaningful because it drives release-please.What changes for contributors
feat:/fix:/feat!:); squash-merge → the title is the release commit.chore: release mainPR that bumpsgo/cmd/root.go+CHANGELOG.md; merging it tagsvX.Y.Z, creates the Release, and attaches binaries.Implementation
release-please-config.json+.release-please-manifest.json— single package., version1.6.0; stampsgo/cmd/root.govia anx-release-please-versionmarker; tagvX.Y.Z.release-please.yml— maintains the release PR; when a release is cut, callsrelease.yml(reusable) to build + attach binaries in the same run (avoids the GITHUB_TOKEN "tags don't trigger workflows" trap).release.yml— now alsoworkflow_call(tag input); the release job creates-or-uploads viagh(works for both manual tag pushes and release-please).pr-title.yml— enforces Conventional Commit PR titles.scripts/{bump-version,new-change,render-changelog}+.changes/. Updated CODEOWNERS, CONTRIBUTING, CLAUDE.md, docs/development, and PR template (also fixed a stalepytestline in the template).Operational notes (repo settings — need a maintainer)
Conventional Commits titleas a required check; set merge to squash-only so PR titles become the release commits.RELEASE_PLEASE_TOKEN(fine-grained PAT: contents + pull-requests write) is optional but recommended so the release PR's checks auto-run; without it, close & reopen the release PR once.v1.6.0and only propose a bump once newfeat:/fix:PRs land.Verified
JSON configs parse;
go build+go test ./cmd/green;grn --versionstill reports1.6.0; no dangling references to the removed tooling.Part of the CLI-onboarding alignment (#1 scaffold #32, #2 conventions #33, this #6). Remaining optional: #4/#5 per-product CLAUDE.md + agent skills.