Skip to content

Draft: Update MacOS platforms up to Sonoma

Jim Kulp requested to merge 3636-update-macos-platforms-up-to-sonoma into develop

What this MR does / why we need it:

Describe what this MR does.

Steps to complete before submitting MR:

  • I have read Contribution guidelines

  • I have ensured I have a changelog written in the imperative form that is meaningful and accurately summarizes the work done

  • I have added the release notes label if applicable (more information below)

  • I have ensured the workflow labels are up to date and will continue to do so up until this work is merged into develop

  • I have added a category, type, and target release label along with all other labels needed

  • My branch is up to date with develop. If it is not, then I have ensured my work does not conflict with other work

  • I agree my bugfix MR does not include new features/enhancements

  • I represent that bugfixes have been locally tested against the most recent major.minor release in which the bug exists

  • (REVIEWER ONLY) I have thoroughly gone through the above steps to ensure that they have been followed

Release Notes

If introducing a change that warrants a release note entry, please add the ~"Release Notes" label and include the release notes in this section. These notes are used to compile the release notes for the target release during the release process. Release notes should be written with the end user as the target audience.

Changelog

Changelog entries are parsed from merge request descriptions and the template below must be followed. Changelog entries must be written in the imperative mood. If there are multiple categories, the categories must be comma separated. Multiple changelog entries must be on their own line, preferably using a bulleted list. Valid "types" correspond to our "type::" labels. Valid categories correspond to our "Category:" labels.

Template:
type(category[,category, ...]): write a short description

Example:

  • feat(devops,tests): add hardware in the loop testing
  • bug(tools): fix broken thing

Which issue(s) this MR closes

Majority of the time a merge request will close an issue. This is usually pre-populated for you by GitLab, but if not the syntax is:
Closes #issue_number, #issue_number2, and #issue_number3

Closes #3636

Merge request reports