Repository navigation
ci(release): skip the publish stage for releases mirrored by ci-bot - #1890
Merged
mergify[bot] merged 1 commit intoOct 6, 2026
Conversation
The test clients' repository (pytest-mergify, rspec-mergify, @mergifyio/*) is now private, so its releases page is gone for users. ci-bot will mirror each of its releases, notes and files, to this repository's releases, as the public place to read them. A release created with a user token starts workflows, so every mirror would run this workflow's publish stage. Those releases carry no CLI binaries, so the asset check would fail each time and block the rest: nothing would reach PyPI, but every mirror would leave a failed run. All three stage-2 jobs now skip releases authored by mergify-ci-bot. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Change-Id: I6cf01a0dcf1f0e532fac48a8bf6d2b3f13c9de5c
Contributor
Merge Protections🟢 All 6 merge protections satisfied — ready to merge. Show 6 satisfied protections🟢 🤖 Continuous Integration
🟢 👀 Review Requirements
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The focused conditions consistently prevent mirrored releases from entering the CLI publication stage.
Review effort: Balanced
Findings: None
What changed in this PR
Prevents mirrored test-client releases from triggering the CLI publication pipeline.
Changes:
- Documents mirrored-release behavior.
- Skips all stage-2 jobs when the release author is
mergify-ci-bot.
| File | Description |
|---|---|
.github/workflows/release.yml |
Adds bot-author guards to binary validation, wheel building, and PyPI publishing. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
kozlek
marked this pull request as ready for review
October 6, 2026 08:16
remyduthu
approved these changes
Oct 6, 2026
sileht
approved these changes
Oct 6, 2026
Contributor
Merge Queue Status
This pull request spent 12 seconds in the queue, including 1 second running CI. Required conditions to merge
|
mergify
Bot
deleted the
devs/kozlek/skip-mirrored-releases/skip-publish-stage-releases-mirrored-ci-bot--6cf01a0d
branch
October 6, 2026 08:21
This branch was successfully deployed
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
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 test clients' repository (pytest-mergify, rspec-mergify, @mergifyio/*)
is now private, so its releases page is gone for users. ci-bot will mirror
each of its releases, notes and files, to this repository's releases, as
the public place to read them.
A release created with a user token starts workflows, so every mirror
would run this workflow's publish stage. Those releases carry no CLI
binaries, so the asset check would fail each time and block the rest:
nothing would reach PyPI, but every mirror would leave a failed run. All
three stage-2 jobs now skip releases authored by mergify-ci-bot.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
🤖 Generated with Claude Code