Skip to content

Run macOS CI on Minerva for verified commits - #3

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
Contributor

Each workflow starts with a route job that calls
RISCfuture/ci-workflows minerva-route.yml at 1.1.0. It sends jobs to
the Minerva self-hosted runner only for verified commits from
RISCfuture and keeps the GitHub-hosted labels for forks, other actors
and unverified commits.

Every macOS job routes to the macOS 26 pool through the output matching
its original label (macos-26): the documentation build, SwiftLint,
Periphery, and the documentation deploy build. The package targets
macOS 26 and no job runs a macOS 27 product, so nothing uses the
macos-27 output. The build matrix routes only legs on Swift 6.4 or
6.4.2; the Swift 6.3 leg stays hosted because setup-swift needs sudo
for other Swift versions. The Linux jobs are unchanged. No job calls
the XCUITestKit reusable workflows.

In the documentation deploy workflow, pages: write and id-token: write
move from the workflow level to the deploy job that uses
actions/deploy-pages. The routed build job gets contents: read only,
as do the route jobs.

🤖 Generated with Claude Code

Each workflow starts with a route job that calls
RISCfuture/ci-workflows minerva-route.yml at 1.1.0. It sends jobs to
the Minerva self-hosted runner only for verified commits from
RISCfuture and keeps the GitHub-hosted labels for forks, other actors
and unverified commits.

Every macOS job routes to the macOS 26 pool through the output matching
its original label (macos-26): the documentation build, SwiftLint,
Periphery, and the documentation deploy build. The package targets
macOS 26 and no job runs a macOS 27 product, so nothing uses the
macos-27 output. The build matrix routes only legs on Swift 6.4 or
6.4.2; the Swift 6.3 leg stays hosted because setup-swift needs sudo
for other Swift versions. The Linux jobs are unchanged. No job calls
the XCUITestKit reusable workflows.

In the documentation deploy workflow, pages: write and id-token: write
move from the workflow level to the deploy job that uses
actions/deploy-pages. The routed build job gets contents: read only,
as do the route jobs.

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