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

Use range dependencies #158

Merged
merged 3 commits into from
Apr 25, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,18 @@
# Changelog

## 0.35.2

- Use range dependencies for `bitcoincore-rpc` and `bitcoin_hashes`

## Release 0.35.1

- Bump MSRV to 1.56.1
- Add `BITCOIND_SKIP_DOWNLOAD` build feature

## Release 0.34.2

- Support Bitcoin Core 26.0

## Release 0.34.1

- Optionally enable ZMQ
Expand Down
6 changes: 3 additions & 3 deletions Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "bitcoind"
version = "0.35.1"
version = "0.35.2"
authors = ["Riccardo Casatta <riccardo@casatta.it>"]
description = "Utility to run a regtest bitcoind process, useful in integration testing environment"
license = "MIT"
Expand All @@ -11,7 +11,7 @@ edition = "2018"
categories = ["cryptography::cryptocurrencies", "development-tools::testing"]

[dependencies]
bitcoincore-rpc = { version = "0.18.0" }
bitcoincore-rpc = { version = ">= 0.17.0, <= 0.19" }
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note, some nuance around the version number 0.19.0:

  • that version does not exist (but cargo is ok with non-existent value in the range)
  • that version has been created locally so we have some confidence that it will exist and will not break the build
  • we don't use some random high number because we don't want to break bitcoind by an unrelated later release of bitcoincore-rpc
  • we have to do a point release bumping the top of the range every time we have an upcoming bitcoincore-rpc release (implies everytime rust-bitcoin is releaseing)

log = "0.4"
which = "4.2.5"
anyhow = "1.0.66"
Expand All @@ -21,7 +21,7 @@ tempfile = "3"
env_logger = "0.9.0"

[build-dependencies]
bitcoin_hashes = { version = "0.13", optional = true }
bitcoin_hashes = { version = ">= 0.13, <= 0.14", optional = true }
flate2 = { version = "1.0", optional = true }
tar = { version = "0.4", optional = true }
minreq = { version = "2.9.1", default-features = false, features = [
Expand Down
Loading