You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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, but cabal.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
Maintaining bounds individually on each library seems quite painful, would there be a way to automate that
Setting too tight bounds might be problematic for wannabe consumers downstream
The text was updated successfully, but these errors were encountered:
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
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: