Skip to content

Run macOS CI on Minerva for verified commits - #9

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, the self-hosted runner, only for verified commits from
RISCfuture. Every other run keeps the hosted labels.

The package targets macOS 26, so no job executes a macOS 27 product
and nothing uses the macos-27 output. The Swift 6.4 test leg, the
documentation build in CI, the documentation deploy build, and
Periphery all run on the macOS 26 pool through the macos-26 output,
which also provides Homebrew for the Periphery install.

The Swift 6.2 macOS test leg stays on its hosted label because
setup-swift needs sudo for that toolchain and Minerva allows sudo
only for xcode-select. The Linux legs, SwiftLint, swift-format,
release, and dof-cycle-watch jobs are unchanged. Cache keys keep
their logical labels.

In the documentation deploy workflow, pages: write and id-token:
write move from the workflow level to the deploy job. The build job
gets contents: read, which is all upload-pages-artifact needs.

No XCUITestKit workflows are used by this repository.

🤖 Generated with Claude Code

A route job from RISCfuture/ci-workflows 1.1.0 sends macOS jobs to
Minerva, the self-hosted runner, only for verified commits from
RISCfuture. Every other run keeps the hosted labels.

The package targets macOS 26, so no job executes a macOS 27 product
and nothing uses the macos-27 output. The Swift 6.4 test leg, the
documentation build in CI, the documentation deploy build, and
Periphery all run on the macOS 26 pool through the macos-26 output,
which also provides Homebrew for the Periphery install.

The Swift 6.2 macOS test leg stays on its hosted label because
setup-swift needs sudo for that toolchain and Minerva allows sudo
only for xcode-select. The Linux legs, SwiftLint, swift-format,
release, and dof-cycle-watch jobs are unchanged. Cache keys keep
their logical labels.

In the documentation deploy workflow, pages: write and id-token:
write move from the workflow level to the deploy job. The build job
gets contents: read, which is all upload-pages-artifact needs.

No XCUITestKit workflows are used by this repository.

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