Skip to content

ci: lift the ubuntu-24.04 hold #90

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
owine merged 1 commit into from
Sep 19, 2026
Merged

ci: lift the ubuntu-24.04 hold #90

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 0 additions & 10 deletions .github/renovate.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,16 +51,6 @@
"docker-compose"
],
"pinDigests": false
},
{
"description": "HOLD - do NOT migrate this repo's GitHub-hosted runners off ubuntu-24.04, and do not delete this rule to 'unblock' a Renovate PR. WHY: ubuntu-26.04 ships Docker Compose 5.1.3; ubuntu-24.04 ships 2.38.2. This repo's lint scripts PARSE the output of `docker compose config` rather than merely checking its exit code - scripts/linting/validate-stack.sh, scripts/linting/lint-summary.sh (which captures and matches on stderr error text), and scripts/linting/validate-image-platforms.sh (which relies on `config --images` emitting exactly one resolved image per line). Compose 5.x is free to reword errors and reshape that output. The lint jobs run on GitHub-hosted runners via `${{ inputs.runner }}`; the deploy jobs run on self-hosted runners with Compose 2.x. Today the two engines match. Bumping only the hosted side would validate stacks with a different Compose engine than the one that actually deploys them - a split that stays GREEN until a stack that lints clean fails to deploy. EXIT CONDITION: remove this rule only once the SELF-HOSTED runners have been upgraded to a Compose 5.x image, then move both sides in one change. Upgrading the hosted side alone is the failure mode this rule exists to prevent. SCOPE: matched on the datasource, not the manager, so it covers both the literal `runs-on:` values (github-actions manager) and the `workflow_call` `runner` input defaults (github-runners customManager) - the two places this repo names a runner label.",
"matchDatasources": [
"github-runners"
],
"matchPackageNames": [
"ubuntu"
],
"enabled": false
}
],
"customManagers": [
Expand Down