Repository navigation
ci: push the latest tag last and build on Ubuntu 26.04 - #2
Merged
Merged
Conversation
- The package page shows the most recently pushed tag; parallel merges let 8.4 win the race
- 26.04 is GA on x64 and arm64; explicit labels keep both arches on the same release
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.
What
Runs the per-version
mergejobs one at a time (max-parallel: 1) so8.5/latestis pushed last, and moves the native build runners toubuntu-26.04/ubuntu-26.04-arm.Why
The GHCR package page builds its "Install from the command line" snippet from the most recently pushed tag. With parallel merges, the last run pushed
8.4at 14:52:32, afterlatest,8.5at 14:52:27, so the page showeddocker pull ...:8.4. Ubuntu 26.04 runners are GA on x64 and arm64, andubuntu-latestis migrating to them through November 19.How
GitHub creates matrix jobs in matrix order, so with
max-parallel: 1theLATEST_PHPversion, which comes last in the matrix, is pushed last. Each merge only runsimagetools create, so serializing them adds roughly 40 seconds. I kept explicit runner labels rather thanubuntu-latest, since no-latestarm label exists and this keeps both architectures on the same release. CLAUDE.md documents both points.Tests
The CI on this PR builds every PHP version on the new 26.04 runners. The package page change can only be checked after the first Publish run on
main.Risk
Low. GitHub documents the order in which matrix jobs are created, not formally the order in which they run. If the order ever drifts, the page shows another tag again, and the images themselves are not affected.
Rollback
Revert the commits. The next Publish run goes back to parallel merges on 24.04 runners.