[release/9.0] Update macOS VM images to use 'latest' version #121391
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR updates the macOS VM images used in Azure Pipelines from a specific version (macos-13) to the latest available version (macos-latest). This ensures the build pipelines use the most current macOS environment.
Key Changes
- Updated both public and internal macOS build pool configurations to use
macos-latestinstead ofmacos-13
| # OSX Public Build Pool (we don't have on-prem OSX BuildPool). | ||
| ${{ if and(in(parameters.osGroup, 'osx', 'maccatalyst', 'ios', 'iossimulator', 'tvos', 'tvossimulator'), eq(variables['System.TeamProject'], 'public')) }}: | ||
| vmImage: 'macos-13' | ||
| vmImage: 'macos-latest' |
There was a problem hiding this comment.
Will this work for Intel? actions/runner-images#13046 mentions
Workflows that depend on x86_64 (Intel CPU) can be migrated to use the macos-15-intel label, which is currently planned as the last supported image based on Intel CPU.
I wasn't sure if they'd handle that for us by using macos-latest
| # OSX Public Build Pool (we don't have on-prem OSX BuildPool). | ||
| ${{ if and(in(parameters.osGroup, 'osx', 'maccatalyst', 'ios', 'iossimulator', 'tvos', 'tvossimulator'), eq(variables['System.TeamProject'], 'public')) }}: | ||
| vmImage: 'macos-13' | ||
| vmImage: 'macos-latest' |
There was a problem hiding this comment.
We don't want these to change underneath us. Using the latest available (15) is good, but we shouldn't use the "latest" tag
|
Superseded by #122422 |
No description provided.