-
Notifications
You must be signed in to change notification settings - Fork 222
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
Set dependency bounds in libraries #4958
Comments
Found this link interesting: https://github.com/wasp-lang/haskell-handbook/blob/master/dependencies-version-bounds.md |
Seems like to complete this we need to complete IntersectMBO/cardano-haskell-packages#1003 |
github-merge-queue bot
pushed a commit
that referenced
this issue
Feb 13, 2025
This pull request bumps our use of the `cardano-wallet-agda` repository to the latest commit. This entails: * Bump `cardano-wallet-read` to version `1.0.0.0`, which is the first version that specifies version constraints in its `.cabal` file. * Bump `customer-deposit-wallet-pure`. In particular, go back to the previous definition of `fromXPubAndCount`. ### Issue #4958
github-merge-queue bot
pushed a commit
that referenced
this issue
Feb 26, 2025
This pull request adds dependency constraints to the `local-cluster` package, as this package is a likely target for releasing on CHaP. Where appropriate, we also remove the direct dependency on the following packages * `extra` because these dependencies do not cross the [Fairbairn threshold](https://wiki.haskell.org/Fairbairn_threshold). ### Issues #4958
This was referenced Feb 26, 2025
github-merge-queue bot
pushed a commit
that referenced
this issue
Feb 28, 2025
This pull request adds dependency constraints to the `launcher` package, as this package is a likely target for releasing on CHaP. Where appropriate, we also remove the direct dependency on the following packages * `either` * `extra` because these dependencies do not cross the [Fairbairn threshold](https://wiki.haskell.org/Fairbairn_threshold). ### Issues #4958
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why
When trying to publish cardano-wallet libraries to CHaP, we realised the lack of dependency bounds inside each library's
.cabal
file is problematic: those dependencies can be updated independently and lead to arbitrary build failures.The cardano-wallet build works because those bounds are set in
cabal.project
at the toplevel, butcabal.project
is ignored.What
Fix dependency bounds inside each library's
.cabal
file, at least on "publishable" libraries : #4411 (comment)The bounds set there will percolate across the dependency graph to impact the whole build.
How
The text was updated successfully, but these errors were encountered: