-
Notifications
You must be signed in to change notification settings - Fork 323
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
Log dependency fix makes use as library very hard #1035
Comments
Looks like this was done in #1009. I think the correct solution is to just pin the version in CI using a CI specific Cargo.lock? On a side note I'd be in favor of not using |
I think other project (LDK, [ "$RUSTC_MINOR_VERSION" -lt 49 ] && cargo update -p log --precise "0.4.18" --verbose |
Sorry, when I pinned |
ffb7c79 ci: Avoid pinning dependencies, use --precise (Daniela Brozzoni) 56b8eea ci: No need to add the llvm repository for wasm (Daniela Brozzoni) Pull request description: Fixes #1035 ### Checklists #### All Submissions: * [x] I've signed all my commits * [x] I followed the [contribution guidelines](https://github.com/bitcoindevkit/bdk/blob/master/CONTRIBUTING.md) * [x] I ran `cargo fmt` and `cargo clippy` before committing ACKs for top commit: evanlinjin: ACK ffb7c79 Tree-SHA512: a2e5e0ffea87dc86e27c2f2f3550e6e6429e66f5fd8e0196e85915de5b0f14f0e4ee9d56c87b38b101eb28d86a65868054c20421f32ecd475ca73d00471e2f8d
bdk depends on
log = "=0.4.18"
, which is really annoying for anyone having another version oflog
in their dependency tree.The text was updated successfully, but these errors were encountered: