Skip to content

chore(deps): update dependency Mergifyio/mergify-cli to 2026.7.21.1#9

Merged
mergify[bot] merged 1 commit into
mainfrom
devs/sileht/setup-cli-mergify-cli-version-bump/update-dep-mergifyio-mergify-cli-2026-7-21-1--ed32dfd0
Jul 22, 2026
Merged

chore(deps): update dependency Mergifyio/mergify-cli to 2026.7.21.1#9
mergify[bot] merged 1 commit into
mainfrom
devs/sileht/setup-cli-mergify-cli-version-bump/update-dep-mergifyio-mergify-cli-2026-7-21-1--ed32dfd0

Conversation

@sileht

@sileht sileht commented Jul 21, 2026

Copy link
Copy Markdown
Member

Bump the pinned default mergify_cli_version from 2026.7.8.1 to the
latest release 2026.7.21.1. Regenerate the README inputs table from
action.yml and move the ci.yaml pinned-install assertions to match.

Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com

Bump the pinned default mergify_cli_version from 2026.7.8.1 to the
latest release 2026.7.21.1. Regenerate the README inputs table from
action.yml and move the ci.yaml pinned-install assertions to match.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Change-Id: Ied32dfd07179dff04713f0a0b5e48707fb016219
@sileht

sileht commented Jul 21, 2026

Copy link
Copy Markdown
Member Author

This pull request is part of a Mergify stack:

# Pull Request Link
1 chore(deps): update dependency Mergifyio/mergify-cli to 2026.7.21.1 #9 👈
2 ci(renovate): keep ci.yaml mergify-cli pin in sync with the action default #10

@mergify

mergify Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Merge Protections

🟢 All 6 merge protections satisfied — ready to merge.

Show 6 satisfied protections

🟢 🤖 Continuous Integration

  • all of:
    • check-success=all-greens

🟢 👀 Review Requirements

  • any of:
    • #approved-reviews-by>=2
    • author = dependabot[bot]
    • author = mergify-ci-bot
    • author = renovate[bot]

🟢 Enforce conventional commit

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:

🟢 🔎 Reviews

  • #changes-requested-reviews-by = 0
  • #review-requested = 0
  • #review-threads-unresolved = 0

🟢 📕 PR description

  • body ~= (?ms:.{48,})

🟢 🚦 Auto-queue

When all merge protections are satisfied, this pull request will be queued automatically.

@mergify
mergify Bot deployed to Mergify Merge Protections July 21, 2026 15:33 Active
@mergify
mergify Bot requested a review from a team July 21, 2026 15:33
@sileht
sileht marked this pull request as ready for review July 21, 2026 17:27
@sileht

sileht commented Jul 21, 2026

Copy link
Copy Markdown
Member Author

@Mergifyio queue

@mergify

mergify Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

  • Entered queue2026-07-22 07:36 UTC · Rule: default · triggered by @sileht with the @mergifyio queue command
  • Checks skipped · PR is already up-to-date
  • Merged2026-07-22 07:36 UTC · at b047baf6d3da436bad8653defbc93664a46375ab · squash

This pull request spent 10 seconds in the queue, including 1 second running CI.

Required conditions to merge

@mergify mergify Bot added the queued label Jul 22, 2026
@mergify
mergify Bot merged commit a81c01e into main Jul 22, 2026
9 checks passed
@mergify mergify Bot removed the queued label Jul 22, 2026
mergify Bot pushed a commit that referenced this pull request Jul 22, 2026
…fault (#10)

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.


Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Depends-On: #9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants