CI and release packaging run on the macOS 14 runner image, which GitHub retires on 2 November

Aberta
  • Algo errado?
#513 3 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
54/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
github-actions, macos, rust
Domínio
ci-cd, release

Direção de pesquisa

Start with .github/workflows/release-package.yml and .github/workflows/ci.yml to locate the three jobs named in the issue, then read scripts/update-hop-compare.py and scripts/ci-release-policy-test.py for the runner and Xcode inventory assumptions. Update the runner references and inventory for macOS 15, preserving the Apple silicon binary’s current minimum macOS version. Done means the policy and minimum-version checks are recorded, and the listed CI and package jobs pass on macOS 15.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

GitHub retires the macos-14 runner image on 2 November 2026 and fails every macos-14 job during scheduled brownouts before that (actions/runner-images#13518). Three of our jobs use that image, including the release package job that builds the Apple silicon release:

  • .github/workflows/release-package.yml job mac ("Apple silicon N and N+1"), runs-on: macos-14
  • .github/workflows/ci.yml job source-home-macos, runs-on: macos-14
  • .github/workflows/ci.yml job release-upstream-assets, matrix entry os: macos-14 (darwin-arm64)

The hosted Mac capacity step also depends on the macOS 14 image: scripts/update-hop-compare.py keeps an allowlist of the Xcode bundles it may remove (CI_XCODE_APPS) and records the macOS 14 image inventory, and scripts/ci-release-policy-test.py pins macos-14.

Why this matters for 2.0.0

The remaining brownouts are 31 October and 1 November, 14:00 to 24:00 UTC (09:00 to 19:00 COT). After 2 November 00:00 UTC (Sunday 1 November, 19:00 COT) every macos-14 job fails. Any CI or package run for a later 2.0.0 candidate, and the CI run on the develop to main pull request, need the newer image. The PR CI run 41142354426 for e4179b0b7 already lost its source-home-macos job to the 30 October brownout (job annotation: "scheduled macOS 14 runner image brownout").

Done means

  • Every macos-14 job runs on macos-15 (Apple silicon, Xcode 16.4 by default), and the policy test pins the new label.
  • The hosted Mac capacity step uses the Xcode bundles of the macOS 15 Apple silicon image and records that image's inventory.
  • The Apple silicon release binary keeps its current minimum macOS version; the change records how that is checked.
  • One CI run on the branch passes source-home-macos and release-upstream-assets (darwin-arm64) on macos-15, and one package run passes the mac job, before the next 2.0.0 candidate is qualified.

Branch: fix/2.0-macos15-runners from e4179b0b7 (the 2.0.0-rc.1 candidate). It merges into the release train after the rc.1 qualification and does not change the rc.1 candidate.

Linguagem predominante
Rust
Estrelas
6
Forks
2
Merge médio
1d 3h
PRs com merge (30d)
42

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de elastos/elastos-runtime

Todas as issues de elastos/elastos-runtime

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.