feat: migrate to Release Please for controlled releases#18
Merged
Conversation
- Add Release Please workflow for creating release PRs - Add separate NPM publish workflow (triggers on GitHub release) - Remove old auto-publish workflow that released on every commit - Update changelog config to only bump versions for feat/fix/perf/refactor - Fix badge workflow repository reference (zenturacp -> dkmaker) - Add RELEASE.md documentation explaining the new release process This change gives maintainers control over when releases happen by requiring them to merge a Release PR, rather than automatically releasing on every push to main.
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
- Claude Code now validates conventional commit format on all PRs - Shows release compliance summary table with each commit's validity - Explains version bump rules to contributors - Provides fix instructions for non-compliant commits - Added git log/show to allowed tools for commit inspection
These files were used by the old TriPSs/conventional-changelog-action which has been replaced by Release Please. Release Please uses its own config in release-please-config.json.
Added '# Changelog' header and cleaned up spacing to match Release Please output format.
- Remove smithery badge from README - Remove Smithery installation instructions - Delete smithery.yaml config file - Delete Dockerfile (was Smithery-generated) - Clean up README structure
- Update npm-publish.yml for trusted publishing: - Add id-token: write permission for OIDC - Upgrade to Node.js 24 (required for npm 11.5.1+) - Remove NODE_AUTH_TOKEN (no longer needed) - Add --provenance flag for supply chain security - Simplify repository field in package.json for provenance
- Weekly npm dependency updates (Mondays) - Weekly GitHub Actions updates - Group minor/patch updates to reduce PR noise - Use conventional commit prefix (chore(deps)) - Separate groups for prod and dev dependencies
The lowercase-only rule was too strict, rejecting valid commits with proper nouns (Release Please, Dependabot) and acronyms (OIDC). Setting to level 0 disables the rule while keeping other validations.
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
This PR migrates the release workflow from automatic releases on every commit to Release Please, giving maintainers control over when releases happen.
Changes
New Files
.github/workflows/release-please.yml- Creates/updates Release PRs automatically.github/workflows/npm-publish.yml- Publishes to NPM when a GitHub release is createdrelease-please-config.json- Release Please configuration.release-please-manifest.json- Version tracking for Release PleaseRELEASE.md- Documentation explaining the release processModified Files
.github/conventional-changelog.config.cjs- Onlyfeat,fix,perf,refactortrigger version bumps.github/workflows/refresh-badges.yml- Fixed repository reference (zenturacp→dkmaker)Removed Files
.github/workflows/publish.yml- Old workflow that released on every commitHow the New Process Works
Why This Change?
ci:,docs:commits caused version bumpsdkmaker/mcp-rest-apiTest Plan
Documentation
See
RELEASE.mdfor full documentation of the new release process.