ci(renovate): keep ci.yaml mergify-cli pin in sync with the action default#10
Merged
Conversation
Member
Author
|
This pull request is part of a Mergify stack:
|
Contributor
Merge Protections🟢 All 7 merge protections satisfied — ready to merge. Show 7 satisfied protections🟢 ⛓️ Depends-On RequirementsRequirement based on the presence of
🟢 🤖 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. |
…fault The pinned-install dogfooding test in ci.yaml hardcoded the mergify_cli_version, but no customManager covered the file, so every mergify-cli release bumped only action.yml + README.md and left ci.yaml stranded on the previous version (as commit 8d75e33 did). Refactor the pinned-install assertion to compare against an EXPECTED_MERGIFY_CLI_VERSION env literal instead of three inline version literals, then add a regex customManager (mirroring the action.yml/README.md ones) that bumps the with: input and the expected env in lockstep. Both matchStrings are anchored to their mergify-specific YAML key, tolerate an optional quote, and require a digit-led value, so they cannot hijack an unrelated quoted assertion or env and leave the neighbouring `latest` install test untouched. Change-Id: Ia4f0d81a819bb8fa2cc205a27d3e38d2197340c5 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
sileht
force-pushed
the
devs/sileht/setup-cli-mergify-cli-version-bump/keep-ci-yaml-mergify-cli-pin-sync-action-default--a4f0d81a
branch
from
July 21, 2026 15:47
46c5501 to
ed45962
Compare
Member
Author
Revision history
|
sileht
marked this pull request as ready for review
July 21, 2026 17:27
kozlek
approved these changes
Jul 22, 2026
remyduthu
approved these changes
Jul 22, 2026
Contributor
Merge Queue Status
|
Contributor
Merge Queue Status
This pull request spent 15 minutes 8 seconds in the queue, including 2 seconds running CI. Required conditions to merge
ReasonPull request #10 could not be retargeted onto the queue base branch HintThis pull request is stacked on another whose head branch still exists after merging, so GitHub never retargeted it onto the queue base branch. Re-push the stack (for example with Requeued — the merge queue status continues in this comment ↓. |
Member
Author
|
@Mergifyio queue |
Contributor
Merge Queue Status
This pull request spent 15 minutes 30 seconds in the queue, including 8 seconds running CI. Required conditions to merge
ReasonPull request #10 could not be retargeted onto the queue base branch HintThis pull request is stacked on another whose head branch still exists after merging, so GitHub never retargeted it onto the queue base branch. Re-push the stack (for example with Requeued — the merge queue status continues in this comment ↓. |
sileht
changed the base branch from
devs/sileht/setup-cli-mergify-cli-version-bump/update-dep-mergifyio-mergify-cli-2026-7-21-1--ed32dfd0
to
main
July 22, 2026 08:50
Member
Author
|
@Mergifyio queue |
Contributor
Merge Queue Status
This pull request spent 19 seconds in the queue, with no time running CI. ReasonThe pull request conflicts with the base branch HintYou should update or rebase your pull request. If you want to requeue this pull request, you can post a Requeued — the merge queue status continues in this comment ↓. |
mergify
Bot
force-pushed
the
devs/sileht/setup-cli-mergify-cli-version-bump/keep-ci-yaml-mergify-cli-pin-sync-action-default--a4f0d81a
branch
from
July 22, 2026 08:51
ed45962 to
e3a334f
Compare
Contributor
|
@sileht this pull request is now in conflict 😩 |
Contributor
Merge Queue Status
This pull request spent 17 seconds in the queue, including 4 seconds running CI. Required conditions to merge
|
mergify
Bot
deleted the
devs/sileht/setup-cli-mergify-cli-version-bump/keep-ci-yaml-mergify-cli-pin-sync-action-default--a4f0d81a
branch
July 22, 2026 08:52
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
3 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 pinned-install dogfooding test in ci.yaml hardcoded the
mergify_cli_version, but no customManager covered the file, so every
mergify-cli release bumped only action.yml + README.md and left ci.yaml
stranded on the previous version (as commit 8d75e33 did).
Refactor the pinned-install assertion to compare against an
EXPECTED_MERGIFY_CLI_VERSION env literal instead of three inline version
literals, then add a regex customManager (mirroring the
action.yml/README.md ones) that bumps the with: input and the expected
env in lockstep. Both matchStrings are anchored to their mergify-specific
YAML key, tolerate an optional quote, and require a digit-led value, so
they cannot hijack an unrelated quoted assertion or env and leave the
neighbouring
latestinstall test untouched.Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com
Depends-On: #9