Repository navigation
Run macOS CI on Minerva for verified commits - #11
Open
RISCfuture wants to merge 1 commit into
Open
RISCfuture wants to merge 1 commit into
RISCfuture wants to merge 1 commit into
Conversation
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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