Remove usage of macos-13 in GitHub Actions

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Infrastructure
    • None
    • 🔵 Done
    • Python Drivers
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      Context

      The macOS 13 runner image will be retired by December 4th, 2025.
      We are currently using it in PyMongo and PyMongoArrow.

      Definition of done

      Move to a supported runner.

      Pitfalls

      From the email:

      What you need to do
      (Recommended) If your workflow is architecture agnostic, you can migrate to any of our arm64 labels:
      macos-15 or macos-latest
      macos-14
      macos-14-xlarge
      macos-latest-xlarge or macos-15-xlarge

      For users that require the x86_64 (Intel) architecture, jobs can be migrated to one of the following labels:
      macos-15-intel (new)
      macos-14-large
      macos-latest-large or macos-15-large

      Notice of macOS x86_64 (Intel) architecture deprecation
      Apple has discontinued support for the x86_64 (Intel) architecture going forward. GitHub will no longer support this architecture on macOS after the macOS 15 runner image is retired in Fall 2027. You should begin migrating your workloads to arm64-based (Apple Silicon) runners as soon as possible to prepare for this eventual deprecation.

            Assignee:
            Alex Clark
            Reporter:
            Steve Silvester
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: