Skip to content

Test against latest GHC point releases, add ghc-9.14.1#212

Open
newhoggy wants to merge 2 commits into
mainfrom
update-ghc-versions
Open

Test against latest GHC point releases, add ghc-9.14.1#212
newhoggy wants to merge 2 commits into
mainfrom
update-ghc-versions

Conversation

@newhoggy

Copy link
Copy Markdown
Member

Aligns tested GHC versions with hw-prim.

Changes

  • tested-with: GHC == 9.14.1, 9.12.4, 9.10.3, 9.8.4, 9.6.7, 9.4.8, 9.2.8, 9.0.2, 8.10.7, 8.8.4
  • CI GHC matrix: ["9.14.1", "9.12.4", "9.10.3", "9.8.4", "9.6.7", "9.4.8"]

Dependency bounds

No bound changes needed: existing upper bounds (base < 5, bytestring < 0.13, text < 3, transformers < 0.7, vector < 0.14, etc.) already admit GHC 9.14 / base-4.22 era boot libraries, and there is no direct containers dependency.

Notes

Local cabal build --enable-tests on an arm64 macOS host fails to resolve dependencies because hw-json-simd (transitive via hw-json-standard-cursor) publishes an intentional base < 0 guard on non-x86_64 architectures. The identical failure occurs on unmodified main, so it is pre-existing/environmental and does not affect x86_64 CI.

John Ky added 2 commits June 12, 2026 19:13
- tested-with: GHC 9.14.1, 9.12.4, 9.10.3, 9.8.4, 9.6.7, 9.4.8, 9.2.8, 9.0.2, 8.10.7, 8.8.4
- CI GHC matrix: 9.14.1, 9.12.4, 9.10.3, 9.8.4, 9.6.7, 9.4.8

Aligns tested GHC versions with hw-prim. Existing dependency bounds
already admit GHC 9.14 / base-4.22 era boot libraries.
GHC 9.14.1 on Windows cannot solve the doctest dependency because
ghc-paths' custom Setup is incompatible with the bundled Cabal 3.16.
GHC 9.4.8 on Windows fails because doctest cannot locate the
chocolatey-installed ghc.exe. Both are upstream/infra issues with no
package-level fix, so exclude those matrix cells.
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