Repository navigation
merge queue: checking #13 on main (a604a73) - #15
Closed
mergify[bot] wants to merge 2 commits into
Closed
mergify[bot] wants to merge 2 commits into
mergify[bot] wants to merge 2 commits 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
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
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.
Note
This is a merge queue draft opened by Mergify. Nobody needs to act on it.
Mergify opened it for batch individual-nougat-d1wtw2 of the
defaultqueue, to test #13 before it merges intomain. Pushing to this branch or closing this pull request removes #13 from the queue.What this draft tests
Mergify checks that #13 still passes CI on top of
main. CI runs on this draft's code, built in this order:mainata604a73🎉 Where it stands: checks passed
CI passed on this draft.
Follow the
defaultqueue in the dashboardWhat happens next
mainand closes this draft.Metadata for CI tooling, read by
mergify ciRequired conditions of queue rule
defaultfor mergeEnforce conventional commit]:title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:👀 Review Requirements]:#approved-reviews-by>=2author = dependabot[bot]author = mergify-ci-botauthor = renovate[bot]📕 PR description]:body ~= (?ms:.{48,})🔎 Reviews]:#changes-requested-reviews-by = 0#review-requested = 0#review-threads-unresolved = 0🤖 Continuous Integration]:check-success=all-greensRequired conditions to stay in the queue
base=mainEnforce conventional commit]:title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:👀 Review Requirements]:#approved-reviews-by>=2author = dependabot[bot]author = mergify-ci-botauthor = renovate[bot]📕 PR description]:body ~= (?ms:.{48,})🔎 Reviews]:#changes-requested-reviews-by = 0#review-requested = 0#review-threads-unresolved = 0🤖 Continuous Integration]:check-success=all-greens