ci: add release-please (automated versioning/releases) — pilot#4
Open
pofallon wants to merge 1 commit into
Open
ci: add release-please (automated versioning/releases) — pilot#4pofallon wants to merge 1 commit into
pofallon wants to merge 1 commit into
Conversation
Pilot of release-please (manifest mode) for climax-mcp: - release-please-config.json: python release-type, 0.x-safe bumps (breaking→minor, feat→patch while <1.0), tags as vX.Y.Z - .release-please-manifest.json: seeded at last stable 0.4.0 - .github/workflows/release-please.yml: opens/updates the Release PR on push to main NOTE: requires Conventional Commits (feat:/fix:/feat!:) to drive releases — release-please stays dormant until such commits land. Also requires the repo setting "Allow GitHub Actions to create and approve pull requests". Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Pilot of release-please for
climax-mcp, to evaluate before rolling out org-wide.What this adds
release-please-config.json— Python release-type;include-component-in-tag: falseso tags arevX.Y.Z(matchesrelease.yml'sv*trigger); 0.x-safe bumps (bump-minor-pre-major,bump-patch-for-minor-pre-major→ breaking=minor, feat=patch while <1.0)..release-please-manifest.json— seeded at the last stable release 0.4.0 (currentpyproject.tomlis0.5.0.dev2; release-please will replace that with a clean managed version on its first release)..github/workflows/release-please.yml— on push tomain, opens/updates a "chore(main): release X.Y.Z" PR; merging it bumpspyproject.toml, updatesCHANGELOG.md, tags, and creates a GitHub Release.Add pagination…, notfeat: add pagination…), so release-please will be dormant untilfeat:/fix:/feat!:commits land. To see it work, the next change should use a conventional prefix (or we add a PR-title linter like deacon'ssemantic-pr.yml).GITHUB_TOKEN(release-please) does not trigger the existingrelease.yml(PyPI publish). To auto-publish we'll either move the publish step into this workflow (gated onrelease_created) or give release-please a PAT. Not wired in this pilot PR — flagged for the rollout decision.🤖 Generated with Claude Code