ci: run GitHub-hosted jobs on ubuntu-26.04 - #320
Merged
Conversation
Pin all three hosted jobs to `ubuntu-26.04`, so the OS each job runs on is a choice made in this repository rather than one GitHub makes when `ubuntu-latest` moves to 26.04 (between 2026-10-19 and 2026-11-19): - ci.yaml `test` (the Python 3.10-3.14 matrix): ubuntu-latest -> 26.04 - ci.yaml `semgrep`: ubuntu-24.04 -> 26.04 - release.yml `pypi-publish`: ubuntu-latest -> 26.04 Nothing is left behind. Every job gets Python from setup-python, and actions/python-versions ships 26.04 builds for all five matrix versions (3.10.21, 3.11.16, 3.12.14, 3.13.15, 3.14.7), so the image's system python3 moving to 3.14 does not reach them. `semgrep` runs in its own container, so the host only supplies Docker. No Node, CMake or system python3 is used, and there is no actionlint here. The required check names do not include the OS, so .mergify.yml is unchanged. `pypi-publish` only runs on a published release and is not exercised by this PR; it runs the same checkout, setup-python and `poetry build` steps as the `test` matrix, which is the proof here. MRGFY-9720 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Change-Id: Ie1144f885aed2126057556dc37831b9c479045e2
Contributor
Merge Protections🟢 All 6 merge protections satisfied — ready to merge. Show 6 satisfied protections🟢 🤖 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. |
jd
marked this pull request as ready for review
September 28, 2026 17:40
kozlek
approved these changes
Sep 28, 2026
Contributor
Merge Queue Status
This pull request spent 38 seconds in the queue, including 2 seconds running CI. Required conditions to merge
|
mergify
Bot
deleted the
devs/jd/jd/mrgfy-9720-sql-compare-move-github-hosted-workflows-to-ubuntu-2604/run-github-hosted-jobs-ubuntu-26-04--e1144f88
branch
September 28, 2026 21:14
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
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.
Pin all three hosted jobs to
ubuntu-26.04, so the OS each job runson is a choice made in this repository rather than one GitHub makes
when
ubuntu-latestmoves to 26.04 (between 2026-10-19 and2026-11-19):
test(the Python 3.10-3.14 matrix): ubuntu-latest -> 26.04semgrep: ubuntu-24.04 -> 26.04pypi-publish: ubuntu-latest -> 26.04Nothing is left behind. Every job gets Python from setup-python, and
actions/python-versions ships 26.04 builds for all five matrix
versions (3.10.21, 3.11.16, 3.12.14, 3.13.15, 3.14.7), so the image's
system python3 moving to 3.14 does not reach them.
semgrepruns inits own container, so the host only supplies Docker. No Node, CMake or
system python3 is used, and there is no actionlint here.
The required check names do not include the OS, so .mergify.yml is
unchanged.
pypi-publishonly runs on a published release and is notexercised by this PR; it runs the same checkout, setup-python and
poetry buildsteps as thetestmatrix, which is the proof here.MRGFY-9720
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com