Skip to content

merge queue: checking #13007 on main (7f9a9f8) - #13049

Closed
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/43fa4c52ba
Closed

mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/43fa4c52ba

Conversation

@mergify

@mergify mergify Bot commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

🎉 This pull request has been checked successfully and will be merged soon. 🎉

#13007 is queued for merge on branch main (7f9a9f8).

This pull request has been created by Mergify to check the mergeability of #13007.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: 7f9a9f842ae6165b5f44e8f2f4308725dd07d20d
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 13007
    scopes: []
scopes: []
...

jd and others added 2 commits September 28, 2026 16:27
Pin all eleven hosted jobs to `ubuntu-26.04`: the nine that pinned
`ubuntu-24.04` in ci.yaml, plus the two `ubuntu-latest` jobs (actionlint in
ci.yaml, deploy in deploy-cf.yaml). An explicit pin is the org convention,
and GitHub moves `ubuntu-latest` to 26.04 on its own schedule between
2026-10-19 and 2026-11-19; pinning now means the switch happens here, with CI
to show it works, rather than on a date nobody chose.

Nothing in these jobs depends on what differs between the 24.04 and 26.04
images. Every Node job installs Node from `.node-version` through
setup-node, so the image's default Node (22 -> 24) is never used. No job
calls system `python3`, CMake, Clang, OpenSSL or PostgreSQL. actionlint runs
as a docker action, and deploy calls a composite Slack action.

actionlint 1.7.8 does not know the 26.04 labels, and neither does any later
release, so `ubuntu-26.04` would fail the actionlint job as an unknown label.
`.github/actionlint.yaml` declares it until actionlint ships it natively.

No job was left behind: this repository has no self-hosted, macOS, Windows
or arm jobs.

deploy-cf.yaml only runs on a push to main, so this pull request's CI does
not exercise it; its single step is a Slack webhook call, which does not
depend on the image.

MRGFY-9715

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Change-Id: Ic6b77c46fff23961ae085d7edb2b86a4c01dac4f
@mergify
mergify Bot deployed to Mergify Merge Protections September 28, 2026 14:44 Active
@mergify mergify Bot closed this Sep 28, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/43fa4c52ba branch September 28, 2026 14:47

This branch was successfully deployed

1 active deployment
Mergify Merge Protections — 34b819ee Deployed Sep 28, 2026 by mergify[bot]
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.

1 participant