Skip to content

Add an on-demand macOS Rust check on the self-hosted runner - #391

Merged
thcp merged 1 commit into
mainfrom
add-macos-check-workflow
Aug 17, 2026
Merged

Add an on-demand macOS Rust check on the self-hosted runner#391
thcp merged 1 commit into
mainfrom
add-macos-check-workflow

Conversation

@thcp

@thcp thcp commented Aug 17, 2026

Copy link
Copy Markdown
Collaborator

Summary

Bootstrapping commit split out of #390 - GitHub only allows dispatching a workflow_dispatch workflow that already exists on the default branch, so this needs to land on main before it can be used to actually verify #390's macOS-specific changes.

ci.yml (PR-triggered) is 100% ubuntu-latest, so code behind #[cfg(target_os = "macos")] has never had a real compiler pass before merging - that cfg-gated code is stripped before semantic analysis even starts on a non-matching target, not just skipped at test time. macos-release.yml already has a real macOS runner, but only fires on release: published and does the full signed/packaged build.

This is deliberately narrow: build/clippy/test only, workflow_dispatch only (not on every PR/push, so the runner's load and cost don't change from today), never touches signing, packaging, or uploads.

Test plan

Purely additive CI config, inert until manually triggered. No app code touched.

ci.yml (PR-triggered) is 100% ubuntu-latest, so code behind
#[cfg(target_os = "macos")] has never had a real compiler pass before
merging - that cfg-gated code is stripped before semantic analysis even
starts on a non-matching target, not just skipped at test time.
macos-release.yml already has a real macOS runner, but only fires on
release: published and does the full signed/packaged build.

This is deliberately narrow: build/clippy/test only, workflow_dispatch only
(not on every PR/push, so the runner's load and cost don't change from
today), never touches signing, packaging, or uploads.
@thcp
thcp merged commit 91f138c into main Aug 17, 2026
10 checks passed
@thcp
thcp deleted the add-macos-check-workflow branch August 17, 2026 20:58
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