Skip to content

Run macOS CI on Minerva for verified commits - #11

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

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

Every macOS job uses the macOS 26 pool through the route output that
matches its original label: the documentation builds in ci.yml and
doc.yml, Periphery, and the macOS Swift 6.4 leg of the build and test
matrix, which runs on macOS 26 for the package's macOS 26 deployment
target. No job needs the macos-27 output, and no job calls an
XCUITestKit workflow.

The macOS Swift 6.2 matrix leg stays on its hosted label because
setup-swift needs sudo for that toolchain, which Minerva does not allow.
Linux jobs are unchanged.

In doc.yml the workflow grants only contents: read. The build job has
contents: read, and the deploy job holds pages: write and id-token:
write for actions/deploy-pages.

🤖 Generated with Claude Code

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

Every macOS job uses the macOS 26 pool through the route output that
matches its original label: the documentation builds in ci.yml and
doc.yml, Periphery, and the macOS Swift 6.4 leg of the build and test
matrix, which runs on macOS 26 for the package's macOS 26 deployment
target. No job needs the macos-27 output, and no job calls an
XCUITestKit workflow.

The macOS Swift 6.2 matrix leg stays on its hosted label because
setup-swift needs sudo for that toolchain, which Minerva does not allow.
Linux jobs are unchanged.

In doc.yml the workflow grants only contents: read. The build job has
contents: read, and the deploy job holds pages: write and id-token:
write for actions/deploy-pages.

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