Repository navigation
ci: move the floating major tag to each new release - #13
Merged
mergify[bot] merged 1 commit intoOct 19, 2026
Merged
mergify[bot] merged 1 commit into
mergify[bot] merged 1 commit into
Conversation
`uses: Mergifyio/setup-cli@v1` resolves the `v1` tag, and nothing has moved that tag since v1.0.0: it still points at the first release, which installs mergify-cli from PyPI through setup-python and uv. Every later release (v1.1.0's prebuilt binary, v1.2.0, v1.3.0) is invisible to anyone following the README's own advice to pin the major. This adds a release workflow that, when a release is published, points the major tag at the newest published release of that major. It picks the newest one rather than the release that triggered it, so a patch on an older minor cannot move `v1` backwards, and prereleases are skipped. The tag is updated through the refs API, so a consumer never sees `v1` missing mid-update. It can also be run by hand with a release tag, which is how `v1` gets moved to v1.3.0 once this lands. The README now says that `v1` follows the v1.x releases and how to stay on one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Change-Id: I879539b0c861a7d1d1a9f2f8cfd66b64419e4361
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. |
JulianMaurin
approved these changes
Oct 17, 2026
kozlek
approved these changes
Oct 19, 2026
Contributor
Merge Queue Status
This pull request spent 1 minute 10 seconds in the queue, including 45 seconds running CI. Required conditions to merge
|
29 of 35 tasks
mergify
Bot
deleted the
devs/jd/jd/followon-111/move-floating-major-tag-release--879539b0
branch
October 19, 2026 08:31
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.
uses: Mergifyio/setup-cli@v1resolves thev1tag, and nothing hasmoved that tag since v1.0.0: it still points at the first release, which
installs mergify-cli from PyPI through setup-python and uv. Every later
release (v1.1.0's prebuilt binary, v1.2.0, v1.3.0) is invisible to anyone
following the README's own advice to pin the major.
This adds a release workflow that, when a release is published, points
the major tag at the newest published release of that major. It picks
the newest one rather than the release that triggered it, so a patch on
an older minor cannot move
v1backwards, and prereleases are skipped.The tag is updated through the refs API, so a consumer never sees
v1missing mid-update. It can also be run by hand with a release tag, which
is how
v1gets moved to v1.3.0 once this lands.The README now says that
v1follows the v1.x releases and how to stayon one.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com