Skip to content

Conversation

peterzhuamazon
Copy link
Member

Description

Remove macos-13 from workflows as it will be deprecated by 2025/11/14

Related Issues

#13417 (comment)

Check List

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@peterzhuamazon peterzhuamazon force-pushed the update-macos-workflows branch from 857c684 to 43a5f31 Compare July 16, 2025 19:01
@peterzhuamazon peterzhuamazon requested review from reta and andrross July 16, 2025 19:02
run: |
# Report success even if previous step failed (Docker on MacOS runner is very unstable)
exit 0;
# GitHub Actions still not supporting arm64 dind yet
Copy link
Member

@andrross andrross Jul 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It appears we have no path forward for assemble coverage on MacOS. That raises the question of why are we removing it now when it will still work for the next 4 months?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can keep the PR open in draft mode until then.
In any way until github actions update their M2 hardware to M3 or above it is hard to get dind run on arm64 macOS.

Thanks.

@peterzhuamazon peterzhuamazon marked this pull request as draft July 17, 2025 15:34
@peterzhuamazon
Copy link
Member Author

Adding @reta to give some ideas on this, also @msfroh .

Thanks.

@reta
Copy link
Contributor

reta commented Jul 17, 2025

Adding @reta to give some ideas on this, also @msfroh .

Thanks @peterzhuamazon , let's keep in draft for now

@msfroh
Copy link
Contributor

msfroh commented Aug 4, 2025

I just noticed this PR as I ran into this same issue over on https://github.com/msfroh/cluster-etcd/pull/10, as I added a dependency on Docker and was using macos-latest.

I was wondering if it would be possible to use self-hosted runners running on one of the cloud providers to get newer Macs. Unfortunately, it looks like AWS doesn't offer M3/M4 Macs yet, and none of the other big cloud providers seem to offer Macs at all (from what I could find).

I did some Googling to see if I could find any options for cloud-based Macs that support M3/M4s. I found this Reddit post with some links to smaller providers that offer M4 Macs with 16GB of RAM for ~$120/month or 99€/month, depending on which one you pick. Of course, then we would need someone to maintain those instances.

@opensearch-trigger-bot
Copy link
Contributor

This PR is stalled because it has been open for 30 days with no activity.

@opensearch-trigger-bot opensearch-trigger-bot bot added the stalled Issues that have stalled label Sep 4, 2025
@peterzhuamazon
Copy link
Member Author

peterzhuamazon commented Sep 18, 2025

I think github has make the latest tag change live now.

@opensearch-trigger-bot opensearch-trigger-bot bot removed the stalled Issues that have stalled label Sep 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 👀 In Review
Status: In review
Development

Successfully merging this pull request may close these issues.

4 participants