Update Mac runners to macos-14 and Xcode to 16.2.

[jonsimantov]

Description

Provide details of the change, and generalize the change in the PR title above.

---

Testing

Describe how you've tested these changes.

---

Type of Change

Place an x the applicable box:

• Bug fix. Add the issue # below if applicable.
• New feature. A non-breaking change which adds functionality.
• Other, such as a build process or documentation change.

---

[gemini-code-assist]

Hello @jonsimantov, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

Hello team, Gemini here to provide a quick summary of this pull request. Based on the title and the changes, this PR aims to update the GitHub Actions workflow configurations to use the newer macos-14 runner image instead of the previous macos-13. This likely includes updating the associated Xcode version available on that runner to 16.2, as mentioned in the title, although the specific patch provided only shows the runner version change. The description is currently empty, so the title and the code changes are the primary source of information for the intent.

Highlights

• CI/CD Configuration Update: The primary change is updating the GitHub Actions configuration to target the macos-14 runner image.
• Runner Version Bump: Specifically, the MACOS_RUNNER variable in the print_matrix_configuration.py script is changed from macos-13 to macos-14.
• Xcode Version (Implied): The PR title also indicates an update to Xcode 16.2, which is the default version expected on the macos-14 runner.

Changelog

• scripts/gha/print_matrix_configuration.py
  • Updated the MACOS_RUNNER variable to use macos-14 instead of macos-13.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

---

Mac runner updated,
New Xcode brings fresh builds,
CI flows smoothly.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the macOS runner image from macos-13 to macos-14 in the GitHub Actions workflow configuration script. This is a common type of update to keep the CI environment current with newer OS versions and associated tooling like Xcode.

The code change itself is a straightforward modification of a constant. However, the pull request description is currently using the template placeholders and lacks essential information. Specifically, details about the testing performed to validate this significant CI infrastructure update, and clarification on the implications for the Xcode version (mentioned as 16.2 in the PR title), are missing. These details are crucial for assessing the impact and readiness of this change.

Summary of Findings

• Incomplete Pull Request Description and Testing Validation: The PR description uses template placeholders and lacks crucial information about how the update to macos-14 was tested. For CI/CD infrastructure changes, detailing the validation process is essential to ensure stability and avoid disruptions. This was raised as a high-severity comment on the relevant code change.
• Clarity on Xcode Version and Selection: The PR title refers to an update to Xcode 16.2. It needs to be clarified whether macos-14 runners provide this version by default or if workflows will require explicit Xcode selection. This is important for ensuring the correct build environment. This concern was included in the high-severity comment.

Merge Readiness

This pull request proposes an update to the macOS runner version, which is a key component of the CI infrastructure. While the code change is simple, the lack of detailed information in the PR description—particularly regarding testing and Xcode version specifics—raises concerns about potential unforeseen impacts on the CI workflows.

I recommend that the PR author provide the requested details by completing the PR description template. Until these points are clarified and adequate testing is confirmed, I would advise against merging this change.

As a reviewer, I am not authorized to approve pull requests. Please ensure that the concerns raised are addressed and that the PR undergoes further review and approval before merging. Due to the high-severity concerns, changes are requested.

[gemini-code-assist]

Updating the MACOS_RUNNER to macos-14 will affect all macOS-based CI jobs. This is a potentially impactful change, and it's important to ensure it's been thoroughly validated. Could you please update the PR description with details on the following points?

1. Testing Conducted:
   • What specific tests or workflows were run using the macos-14 runner to confirm compatibility and correctness?
   • Were there any issues encountered during testing, and how were they resolved?
2. Xcode Version Confirmation: The PR title mentions an update to "Xcode to 16.2".
   • Does the macos-14 runner image, by default, provide Xcode 16.2, or a version that meets the project's requirements and aligns with this target?
   • If Xcode 16.2 (or another specific version) is critical and not the default on macos-14, will corresponding changes be made in the workflow files to explicitly select it (e.g., using xcode-select)? This script only defines the runner image string.
3. Potential Impact:
   • Are there any known compatibility issues or special considerations with macos-14 or the new Xcode version that might affect the project's build, tests, or deployment processes?

Providing this information in the PR description will greatly help in understanding the change's scope and verifying its stability.