Problem
The CI workflow uses haskell-actions/setup@v2 with enable-stack: true and stack-version: latest. The latest resolves to stack 3.9.3, which GHCup cannot install on the runner:
[ Error ] [GHCup-00130] The version "3.9.3" of the tool stack is not installed.
Impact
This blocks ALL new PRs from first-time contributors and cache-miss builds. It does NOT affect master because master has a GHCup cache from before the metadata issue.
Root Cause
The runner has GHCup binary version 0.2.6.2, which uses a metadata file that lists stack 3.9.3 as available. However, the actual binary for 3.9.3 is not downloadable (stackage metadata/CI infrastructure mismatch).
Workaround Used
In our PR (#8611), we worked around this by:
- Setting
enable-stack: false in the build job (use system stack)
- Removing
haskell-actions/setup@v2 from test jobs entirely (they don't need GHC/stack)
Proposed Fix
Either:
- Pin
stack-version to a known-working version (e.g., 3.7.1 or 3.11.1)
- Or upgrade the runner's GHCup binary to the latest version
- Or remove
haskell-actions/setup@v2 and use pre-installed system stack
Problem
The CI workflow uses
haskell-actions/setup@v2withenable-stack: trueandstack-version: latest. Thelatestresolves to stack 3.9.3, which GHCup cannot install on the runner:Impact
This blocks ALL new PRs from first-time contributors and cache-miss builds. It does NOT affect master because master has a GHCup cache from before the metadata issue.
Root Cause
The runner has GHCup binary version 0.2.6.2, which uses a metadata file that lists stack 3.9.3 as available. However, the actual binary for 3.9.3 is not downloadable (stackage metadata/CI infrastructure mismatch).
Workaround Used
In our PR (#8611), we worked around this by:
enable-stack: falsein the build job (use system stack)haskell-actions/setup@v2from test jobs entirely (they don't need GHC/stack)Proposed Fix
Either:
stack-versionto a known-working version (e.g., 3.7.1 or 3.11.1)haskell-actions/setup@v2and use pre-installed system stack