Repository navigation
Run macOS CI on Minerva for verified commits - #3
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 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
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 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