Skip to content

Run macOS CI on Minerva for verified commits - #24

Open
RISCfuture wants to merge 1 commit into
mainfrom
ci/minerva
Open

RISCfuture wants to merge 1 commit into
mainfrom
ci/minerva

Conversation

@RISCfuture

Copy link
Copy Markdown
Owner

A route job from RISCfuture/ci-workflows 1.1.0 sends macOS jobs to
Minerva only for verified commits from RISCfuture and keeps the hosted
labels for forks, other actors and unverified commits. Each workflow
that routes declares the route job with contents: read.

Every routed job goes to the macOS 26 pool through the output matching
its original label: the Swift 6.4 macos-26 leg of the test matrix, the
documentation build in ci.yml, the Pages build in doc.yml, and the
Periphery scan, which installs Periphery with Homebrew. The package
targets macOS 15, so nothing here needs the macOS 27 pool.

The macos-15 and Swift 6.3 legs stay hosted because setup-swift needs
sudo for any Swift other than 6.4. The Linux, SwiftLint, swift-format
and release jobs are not macOS jobs and are unchanged.

In doc.yml the workflow grants only contents: read. The routed build
job declares contents: read and the deploy job declares pages: write
and id-token: write, so the job that runs on self-hosted hardware holds
no Pages or OIDC token. No XCUITestKit workflows are called.

🤖 Generated with Claude Code

A route job from RISCfuture/ci-workflows 1.1.0 sends macOS jobs to
Minerva only for verified commits from RISCfuture and keeps the hosted
labels for forks, other actors and unverified commits. Each workflow
that routes declares the route job with contents: read.

Every routed job goes to the macOS 26 pool through the output matching
its original label: the Swift 6.4 macos-26 leg of the test matrix, the
documentation build in ci.yml, the Pages build in doc.yml, and the
Periphery scan, which installs Periphery with Homebrew. The package
targets macOS 15, so nothing here needs the macOS 27 pool.

The macos-15 and Swift 6.3 legs stay hosted because setup-swift needs
sudo for any Swift other than 6.4. The Linux, SwiftLint, swift-format
and release jobs are not macOS jobs and are unchanged.

In doc.yml the workflow grants only contents: read. The routed build
job declares contents: read and the deploy job declares pages: write
and id-token: write, so the job that runs on self-hosted hardware holds
no Pages or OIDC token. No XCUITestKit workflows are called.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant