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

Offen
  • Stimmt etwas nicht?
#513 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
54/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
github-actions, macos, rust
Bereich
ci-cd, release

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Rust
Sterne
6
Forks
2
Ø Merge
1 T. 3 Std.
Gemergte PRs (30 T.)
42

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus elastos/elastos-runtime

Alle Issues in elastos/elastos-runtime

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.