Repository navigation
ci: pin release verification to Ubuntu 24.04 - #49
Merged
Merged
Conversation
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 CI and x64 release jobs to Ubuntu 24.04, matching the existing ARM64 runner family. The ubuntu-latest migration to 26.04 coincided with browser dependency downloads taking over 15 minutes on affected runners. A fixed OS label makes the build/test environment predictable; application dependencies, source, assertions, permissions, offline checks and native image gates remain unchanged.
Also clarify that the V1 role's proxy flag controls only controller downloads, while the direct entry_favicon module's use_proxy is inherited by Ansible fetch_url for portal requests too. No host proxy environment is changed.
The existing workflow-dispatch path will rebuild immutable tag v2.4.2 with this infrastructure after CI passes. Its exact-source and app/collection-version checks stay in place; no release tag rewrite or product version change is needed.
Validation: workflow YAML parses, the only workflow changes are fixed runner labels, and the full existing 191 app/HTTP, 21 browser, 18 Python, collection integration and offline image gates run on this PR.