Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix #58: Let's try haskell-ci #59

Merged
merged 1 commit into from
Oct 5, 2024
Merged

fix #58: Let's try haskell-ci #59

merged 1 commit into from
Oct 5, 2024

Conversation

supki
Copy link
Owner

@supki supki commented Oct 4, 2024

No description provided.

@supki supki force-pushed the feature/58-ci branch 4 times, most recently from 318a4aa to c855282 Compare October 4, 2024 21:38
@supki
Copy link
Owner Author

supki commented Oct 4, 2024

As per usual for anything related to cabal nothing works unless properly massaged. Currently stuck at ghc-9.6.4: could not execute: hspec-discover, which I assume requires another inane configuration line in *.cabal.

@supki
Copy link
Owner Author

supki commented Oct 4, 2024

Apparently, at least cabal can now use stackage snapshots for dependency resolution using the cabal.project file, e.g.:

packages: .
import: https://www.stackage.org/lts-22.27/cabal.config

(haven't tested yet)

@supki supki force-pushed the feature/58-ci branch 4 times, most recently from ea1bff3 to fb03cb9 Compare October 5, 2024 19:29
@supki
Copy link
Owner Author

supki commented Oct 5, 2024

I had to ignore failures in the cabal check step because I'm simply not going to add the upper bounds for my dependencies.

@supki supki merged commit f05c264 into main Oct 5, 2024
4 checks passed
@supki supki deleted the feature/58-ci branch October 5, 2024 20:02
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