Skip to content

Drop macOS from CI matrix - #30

Merged
m-col merged 1 commit into
masterfrom
fix-macos-ci
Aug 30, 2026
Merged

Drop macOS from CI matrix#30
m-col merged 1 commit into
masterfrom
fix-macos-ci

Conversation

@m-col

@m-col m-col commented Aug 30, 2026

Copy link
Copy Markdown
Owner

Summary

  • ci.yaml's macOS-latest job has been failing: Stack's resolver (lts-19.5) pins GHC 9.0.2, and Stack downloads its own isolated copy of that GHC rather than using the one haskell-actions/setup installs via ghcup. That isolated GHC 9.0.2 can't find working LLVM tools (ld/opt) on GitHub's macOS-latest runners, which are now Apple Silicon (arm64), so Setup.hs fails to compile before any project code builds.
  • This was previously masked by the actions/cache@v2 deprecation error aborting the job before it reached the build step.
  • Rather than bump the pinned GHC/resolver version (a larger, riskier change with its own compatibility risk on arm64 macOS), this drops macOS-latest from the matrix. ubuntu-latest already covers build/test/docs generation and deployment.

Test plan

  • Confirm the ci job runs green on ubuntu-latest only
  • Confirm Generate docs/Deploy docs still run on push to master

Generated by Claude Code

Stack's resolver pins GHC 9.0.2, which fails to build on GitHub's
macOS-latest runners now that they're Apple Silicon (arm64) - the
isolated GHC Stack downloads can't find working LLVM tools there.
ubuntu-latest already covers the build/test/docs pipeline; dropping
macOS avoids a permanently red CI job rather than bumping the
resolver, which is a larger, riskier change.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UyGjWEMRv9qKWKmXJfgW7v
@m-col
m-col merged commit 97e8503 into master Aug 30, 2026
1 check passed
@m-col
m-col deleted the fix-macos-ci branch August 30, 2026 20:40
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.

2 participants