Avoid using *-latest for runner images
#71201
Open
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
While using the `ubuntu-latest`, `macos-latest`, and `windows-latest` runner image tags is convenient, it has proven to be problematic in a number of instances as the runners are slowly updated (see Core-62808 and Core-62843). Additionally, GitHub uses warnings on workflow runs using the `-latest` tags when there are upcoming changes to the images that the alias points to. There is no way to acknowledge and dismiss these notices, and they can be quite noisy and alarming. This switches all workflows to using specific version tags representing the latest non-preview versions, which currently are as follows: - `ubuntu-24.04` - `windows-2025` - `macos-15`
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
desrosj
added
the
[Type] Automated Testing
|
Size Change: 0 B Total Size: 1.92 MB ℹ️ View Unchanged
|
johnbillion
approved these changes
Aug 14, 2025
|
Flaky tests detected in a3effc6. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/16970285834
|
This makes helps avoid needing to change the required check every time the runner is updated.
|
I've also updated the job names to only include the OS type without a version. Since we don't need to test against multiple versions of an OS, this eliminates the need to change the configured required checks for the repository with each update. |
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?
This switches all workflows to using specific version tags representing the latest non-preview versions, which currently are as follows:
ubuntu-24.04windows-2025macos-15Why?
While using the
ubuntu-latest,macos-latest, andwindows-latestrunner image tags is convenient, it has proven to be problematic in a number of instances as the runners are slowly updated (see Core-62808 and Core-62843).Additionally, GitHub uses warnings on workflow runs using the
-latesttags when there are upcoming changes to the images that the alias points to. There is no way to acknowledge and dismiss these notices, and they can be quite noisy and alarming.