Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GHA docs say macos-latest is macos-14 (M1) but it is instead macos-12 (Intel) #9640

Closed
3 of 13 tasks
cclauss opened this issue Apr 5, 2024 · 2 comments
Closed
3 of 13 tasks
Labels
bug report documentation Improvements or additions to documentation

Comments

@cclauss
Copy link

cclauss commented Apr 5, 2024

Description

The macos-latest label currently uses the macOS 14 runner image.

https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-public-repositories

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • macOS 11
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • Windows Server 2019
  • Windows Server 2022

Image version and build link

macos-latest and macos-14

macOS (macos-latest)
Current runner version: '2.315.0'
Operating System
macOS
12.7.4
21H1123
Runner Image
Image: macos-12


macOS (macos-14)
Current runner version: '2.315.0'
Operating System
macOS
14.4.1
23E224
Runner Image
Image: macos-14-arm64

Is it regression?

No

Expected behavior

It would be GREAT if M1 was the default but I sense that the default is still Intel.

Actual behavior

Docs are incorrect.

Repro steps

Run a GHA with macos-latest and look at set up job.

@mikhailkoliada mikhailkoliada added documentation Improvements or additions to documentation and removed needs triage labels Apr 5, 2024
@mikhailkoliada
Copy link
Contributor

@cclauss Hey! Please report to https://github.com/orgs/community/discussions (cc @Steve-Glass) as we do not maintain GitHub docs directly

@mikhailkoliada
Copy link
Contributor

@cclauss actually no need to report, I clarified our docs a bit, #9642

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants