Release bdk-cli-1.0.0

[tvpeter]

Create a new major release

Summary

This release of bdk-cli 1.0.0 uses bdk_wallet 1.0.0 and integrates Kyoto, which uses the Kyoto protocol for compact block filters. It sets SQLite as the default database and drops support for sled.

Commit

Changelog

• Change MSRV to 1.75.0 by @notmandatory in 50a6a60
• change electrum client to use bdk_electrum, sqlite feature to use bdk_wallet/rusqlite by @tvpeter in 6f263bf
• update repl to use shlex instead of regex, rustyline and fd-lock by @notmandatory in 50a6a60
• update bdk_wallet to 1.0.0 by @tvpeter in 6f263bf
• update bdk_bitcoind_rpc to 0.18.0, bdk_electrum to 0.21.0, bdk_esplora to 0.20.1, bdk-reserves to 0.29.0 by @tvpeter in 6f263bf
• update electrsd to v31.0 by @tvpeter in 58f07a1
• update clap to v4.5 by @notmandatory in 50a6a60
• add cbf feature usingbdk-kyoto by @rustaceanrob in 8ac6957 and @tvpeter in 6debc68
• replace regtest-bitcoin feature with rpc by @tvpeter in 8307db0
• add custom error enum by @tvpeter in b8d2357
• sets repl and sqlite as the default features by @notmandatory in 50a6a60
• Set default fee rate to FeeRate::BROADCAST_MIN by @tvpeter in ddce50d
• enable rbf by default by @tvpeter in 4c89cbf
• replace ExtendedPrivateKey with Xpriv by @tvpeter in 4c89cbf
• Replace list_transactions with transactions by @tvpeter in ddce50d
• Replace allow_shringking with drain_to methods by @tvpeter ddce50d
• Replace Wallet<D> with PersistedWallet<D> by @tvpeter in ddce50d
• replacedescriptor CLI parameter with ext-descriptor and change with int-descriptor
• drop support for sled
• Drop key-value-db feature by @tvpeter in b56c023
• drop esplora-ureq, esplora-reqwest, regtest-bitcoin, regtest-electrum, regtest-node and reserves features by @notmandatory in 50a6a60

Checklist

Release numbering must follow Semantic Versioning. These steps assume the current master
branch development version is MAJOR.MINOR.0.

On the day of the feature freeze

Change the master branch to the next MINOR+1 version:

• Switch to the master branch.
• Create a new PR branch called bump_dev_MAJOR_MINOR+1, eg. bump_dev_0_22.
• Bump the bump_dev_MAJOR_MINOR+1 branch to the next development MINOR+1 version.
  • Change the Cargo.toml version value to MAJOR.MINOR+1.0.
  • The commit message should be "Bump version to MAJOR.MINOR+1.0".
• Create PR and merge the bump_dev_MAJOR_MINOR+1 branch to master. Chore/make release #188
  • Title PR "Bump version to MAJOR.MINOR+1.0".

On the day of the release

Tag and publish new release:

• Double check that your local master is up-to-date with the upstream repo.
• Create a new branch called release/MAJOR.MINOR+1 from master.
• Add a tag to the HEAD commit in the release/MAJOR.MINOR+1 branch.
  • The tag name should be vMAJOR.MINOR+1.0
  • The first line of the tag message should be "Release MAJOR.MINOR+1.0".
  • In the body of the tag message put a copy of the Summary and Changelog for the release.
  • Make sure the tag is signed, for extra safety use the explicit --sign flag.
• Wait for the CI to finish one last time.
• Push the new tag to the bitcoindevkit/bdk-cli repo.
• Publish all the updated crates to crates.io.
• Create the release on GitHub.
  • Go to "tags", click on the dots on the right and select "Create Release".
  • Set the title to Release MAJOR.MINOR+1.0.
  • In the release notes body put the Summary and Changelog.
  • Use the "+ Auto-generate release notes" button to add details from included PRs.
  • Until we reach a 1.0.0 release check the "Pre-release" box.
• Make sure the new release shows up on crates.io and that the docs are built correctly on docs.rs.
• Announce the release, using the Summary, on Discord, Twitter and Mastodon.
• Celebrate 🎉

[notmandatory]

Fix by #188