feat(ci): replace semantic-release with release-please - #16
Open
caio-pizzol wants to merge 2 commits into
Open
Conversation
semantic-release pushed version-bump commits directly to main, which branch protection now rejects (PR-only + required cubic check). Release Please routes the bump/changelog through a normal PR instead: merge it and the tags + GitHub releases are created. Manifest seeded at the current mcp-v1.3.0 / web-v1.3.0 tags; component tag prefixes preserved. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
caio-pizzol
marked this pull request as ready for review
August 11, 2026 21:45
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d06b21ad4a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
All reported issues were addressed across 7 files
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
… versions issues:write is needed for release-please's PR labeling. packages/shared ships inside the MCP server, so it's registered as a package and version- linked to mcp: shared-only commits now cut an mcp-v* release again (the old semantic-release analyzed commits repo-wide). linked-versions is used instead of node-workspace to avoid rewriting workspace:* dep specs. Co-Authored-By: Claude Fable 5 <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
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.
The Release workflow started failing after branch protection was added to main: semantic-release's
@semantic-release/gitstep pushes version-bump commits directly to main, which is now rejected (GH006— PR-only + required cubic check; see run 31536502759). Release Please fixes this structurally: version bumps and changelogs land via a normal release PR that goes through the same protection as everything else, and tags + GitHub Releases are created when that PR merges.Changes
release.yml→ singlegoogleapis/release-please-action@v4job (manifest mode)release-please-config.json+.release-please-manifest.json: two node packages,apps/mcp-serverandapps/web, seeded at their current versions (both 1.3.0); tag series continue asmcp-v*/web-v*apps/*/.releaserc.json, the rootreleasescript, and the five semantic-release devDependencies (lockfile updated)pathsfilter — release-please decides per-package relevance from commit file paths itself, and the release PR's own merge (root manifest files) must also trigger the workflowprepareCmdbuild check is covered by CI running on the release PRFollow-up needed (repo settings, not in this PR): add a
RELEASE_PLEASE_TOKENsecret (PAT or GitHub App token with contents+PR write). The workflow falls back togithub.token, but PRs opened with it don't trigger the CI workflow, so the requiredcheckstatus would be missing on release PRs until the secret exists (close/reopen the release PR as a manual workaround).Must stay the same: tag formats
mcp-v*/web-v*; deploys remain manual (bun run deploy/ wrangler) — this PR only changes versioning/release automation.Review: check the manifest paths/versions against the existing tags. Ignore the biome warning in scripts/ingest-xsd (pre-existing).
Verified:
bun install→ 5 packages removed;bun run typecheck→ clean; lefthook pre-commit (build/format/lint/typecheck) → all green🤖 Generated with Claude Code