Repository navigation
Conversation
- The workflow init writes now uses runs-on: ubuntu-24.04 instead of ubuntu-latest - A runner image migration can no longer change the toolchain in a file we cannot update in customer repos - Our own CI stays on ubuntu-latest - Refs localheroai/localhero-ai#724
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.
Why
GitHub moves
ubuntu-latestto the Ubuntu 26 image between October 19 and November 19. The workflowinitwrites lives in the customer's repository, so if a future image changes the toolchain under it (the Django path installsgettextfrom apt), we cannot fix the file for them. Pinningubuntu-24.04keeps that toolchain fixed for the two years GitHub supports the image.Trade-off: pinned workflows age out. In about two years every repo created with this version needs a manual bump, or it stops running when GitHub retires the image.
Change
src/utils/github.ts: the generated job usesruns-on: ubuntu-24.04via aRUNNER_IMAGEconstant.tests/utils/github.test.ts(written first, failed onubuntu-latest).Our own CI (
.github/workflows/test.yml) stays onubuntu-latest: breakage there is visible to us and cheap to fix. Existing customer workflows are unchanged either way.Evidence from Ubuntu 26
django-trial-rig PR localheroai/django-trial-rig#12, run 37839209218,
runs-on: ubuntu-26.04(imageubuntu-26.04version20260927.149.1, Ubuntu 26.04.1 LTS), CLI 0.0.80:sudo apt-get install -y -qq gettextinstalledgettext 0.23.2-1without anapt-get updateactions/setup-python@v5with 3.12:Successfully set up CPython (3.12.14),pip 26.2.1makemessages --keep-pot -l sv -l ru -l pl: processed all three localesUpdated 1 keys in 3 languages, commit pushed to the PR branchsetup-uv@v5installed uv 0.12.24,uv pip installplusuv run python manage.py makemessagesupdated the.potand all three.pofilesVerified
npm test: 82 suites, 1496 tests passnpx tsc --noEmit,npx eslint 'src/**/*.ts': cleanCompanion server change for the setup PR: localheroai/localhero-ai#875. If this is approved, the workflow examples on the docs pages and blog posts still say
ubuntu-latestand need a follow-up.