On Fri, Dec 06, 2024 at 06:39:59AM -0500, karthik nayak wrote: > Patrick Steinhardt <ps@xxxxxx> writes: > > > The macOS Ventura images we use for GitLab CI runners have been > > deprecated. Update them to macOS 14, aka Sonoma. > > > > Signed-off-by: Patrick Steinhardt <ps@xxxxxx> > > --- > > .gitlab-ci.yml | 4 ++-- > > 1 file changed, 2 insertions(+), 2 deletions(-) > > > > diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml > > index 526ecfe030a43e0a5a83ddd35cb7c96d46ab2485..61c56ccac8fdc940075d91dd4cb0b54ee33d5199 100644 > > --- a/.gitlab-ci.yml > > +++ b/.gitlab-ci.yml > > @@ -99,10 +99,10 @@ test:osx: > > parallel: > > matrix: > > - jobname: osx-clang > > - image: macos-13-xcode-14 > > + image: macos-14-xcode-15 > > CC: clang > > - jobname: osx-reftable > > - image: macos-13-xcode-14 > > + image: macos-14-xcode-15 > > CC: clang > > artifacts: > > paths: > > The changes look good, the documentation also states that if no image is > mentioned, it'll use `macos-14-xcode-15` [1]. I wonder if this means > that if the image is unspecified, it will always use the first > non-deprecated version. That'd allow us to not have to keep updating > this. > > [1]: https://docs.gitlab.com/ee/ci/runners/hosted_runners/macos.html#supported-macos-images It does, but at the cost of potential breakage whenever GitLab decides to update these images. It shouldn't happen all that frequently, but when we notice that it does become annoying we can iterate in the past and experiment with setting no image at all. Patrick
