ci(release): restore prerelease guard on retry-sign-release publish jobs (MCP-3020)#743
Conversation
…obs (MCP-3020) Re-target of #737 to main. The original PR was based on the already-merged fix/mcp-2905 branch and merged there, so the guard never reached main. Skips update-homebrew and publish-linux-repos in retry-sign-release.yml for prerelease tags (containing '-', e.g. -rc.*), mirroring release.yml — prevents the retry path from publishing prerelease artifacts to stable channels. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Deploying mcpproxy-docs with
|
| Latest commit: |
8b8f77a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f3450e5e.mcpproxy-docs.pages.dev |
| Branch Preview URL: | https://fix-mcp-3020-prerelease-guar-m7bl.mcpproxy-docs.pages.dev |
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
📦 Build ArtifactsWorkflow Run: View Run Available Artifacts
How to DownloadOption 1: GitHub Web UI (easiest)
Option 2: GitHub CLI gh run download 27933278078 --repo smart-mcp-proxy/mcpproxy-go
|
There was a problem hiding this comment.
✅ Gatekeeper approval — review verdict: ACCEPT (by KimiReviewer, model-diverse fallback).
This approval is posted automatically by the MCPProxy Gatekeeper App on behalf of KimiReviewer — the model-diverse reviewer-fallback reviewer of record (verdict lives in the Paperclip review thread). Author≠approver satisfied; QA + CI gates enforced separately.
Auto-approved per Model B (MCP-1249) + reviewer-fallback (MCP-3066).
Re-target of #737 to main. The original #737 was based on the already-merged
fix/mcp-2905branch and merged there, so the guard never landed on main (caught while cutting v0.44.0).Change
Adds
&& !contains(inputs.tag, '-')to theupdate-homebrewandpublish-linux-reposjobs inretry-sign-release.yml, so the retry path skips publishing to stable Homebrew/Linux channels for prerelease tags (-rc.*/-next.*) — mirroring the guard already inrelease.yml.Scope
Failure-retry path only; does not affect the primary release.yml flow. Supersedes #737 (which should be closed — it merged into a dead branch).
🤖 Generated with Claude Code