Skip to content

ci: move GitHub-hosted Linux jobs to Ubuntu 26.04 - #56

Merged
mergify[bot] merged 1 commit into
mainfrom
devs/jd/jd/mrgfy-9736-homebrew-tap-move-github-hosted-workflows-to-ubuntu-2604/move-github-hosted-linux-jobs-ubuntu-26-04--55b77db7
Oct 1, 2026
Merged

mergify[bot] merged 1 commit into
mainfrom
devs/jd/jd/mrgfy-9736-homebrew-tap-move-github-hosted-workflows-to-ubuntu-2604/move-github-hosted-linux-jobs-ubuntu-26-04--55b77db7

Conversation

@jd

@jd jd commented Sep 28, 2026

Copy link
Copy Markdown
Member

Pins every hosted Linux job in tests.yml to 26.04:

  • test-bot x86_64 leg: ubuntu-latest -> ubuntu-26.04
  • test-bot arm64 leg: ubuntu-24.04-arm -> ubuntu-26.04-arm
  • all-greens: ubuntu-latest -> ubuntu-26.04

The macOS jobs (macos-26, macos-15-intel) stay as they are.

Explicit pins are 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 we find out about a breakage on a PR instead of on a random day in
November.

The two test-bot Linux legs run inside ghcr.io/homebrew/brew:main, so the
host only supplies Docker (29 on 26.04) and the runner's Node for the JS
actions. The image's Python, CMake, compilers and so on never reach the
job. The x86_64 leg would flip to 26.04 in November anyway, and I moved
the arm64 leg alongside it so both Linux legs stay on the same image.
all-greens only runs gha-mergify-ci's wait-jobs.

Side effect: the RubyGems cache key includes matrix.os, so the first
run on each new label starts with a cold cache.

How to verify: test-bot skips draft PRs, so while this PR is a draft only
all-greens runs on the new label. Taking it out of draft runs both
test-bot Linux legs on 26.04, and a green run there is the proof.

Refs: MRGFY-9736

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com

Pins every hosted Linux job in tests.yml to 26.04:

- test-bot x86_64 leg: ubuntu-latest -> ubuntu-26.04
- test-bot arm64 leg: ubuntu-24.04-arm -> ubuntu-26.04-arm
- all-greens: ubuntu-latest -> ubuntu-26.04

The macOS jobs (macos-26, macos-15-intel) stay as they are.

Explicit pins are 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 we find out about a breakage on a PR instead of on a random day in
November.

The two test-bot Linux legs run inside ghcr.io/homebrew/brew:main, so the
host only supplies Docker (29 on 26.04) and the runner's Node for the JS
actions. The image's Python, CMake, compilers and so on never reach the
job. The x86_64 leg would flip to 26.04 in November anyway, and I moved
the arm64 leg alongside it so both Linux legs stay on the same image.
all-greens only runs gha-mergify-ci's wait-jobs.

Side effect: the RubyGems cache key includes matrix.os, so the first
run on each new label starts with a cold cache.

How to verify: test-bot skips draft PRs, so while this PR is a draft only
all-greens runs on the new label. Taking it out of draft runs both
test-bot Linux legs on 26.04, and a green run there is the proof.

Refs: MRGFY-9736

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Change-Id: I55b77db78beeac1dd31c3f26f1796a26043c7f4a
Copilot AI lite review requested due to automatic review settings September 28, 2026 15:03
@mergify
mergify Bot deployed to Mergify Merge Protections September 28, 2026 15:03 Active
@mergify

mergify Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

Merge Protections

🟢 All 6 merge protections satisfied — ready to merge.

Show 6 satisfied protections

🟢 🤖 Continuous Integration

  • check-success = all-greens

🟢 👀 Review Requirements

  • #approved-reviews-by >= 2

🟢 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.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@jd
jd marked this pull request as ready for review September 28, 2026 15:33
@jd
jd requested a review from a team September 29, 2026 20:39
@jd
jd requested a review from a team October 1, 2026 14:13
@mergify

mergify Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

Merge Queue Status

  • ✅ Entered queue — 2026-10-01 15:25 UTC · Rule: default · triggered by merge protections
  • ✅ Checks skipped · PR is already up-to-date
  • ✅ Merged — 2026-10-01 15:25 UTC · at 821a7c548aa6a45b55c83bbde2a3509fa2cff82b · squash

This pull request spent 12 seconds in the queue, including 2 seconds running CI.

Required conditions to merge

@mergify mergify Bot added the queued label Oct 1, 2026
@mergify
mergify Bot merged commit 821a7c5 into main Oct 1, 2026
10 of 11 checks passed
@mergify
mergify Bot deleted the devs/jd/jd/mrgfy-9736-homebrew-tap-move-github-hosted-workflows-to-ubuntu-2604/move-github-hosted-linux-jobs-ubuntu-26-04--55b77db7 branch October 1, 2026 15:25
@mergify mergify Bot removed the queued label Oct 1, 2026

This branch was successfully deployed

1 active deployment
Mergify Merge Protections — 5465d37b 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.

4 participants