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
This is the final "beta" test release before a final bdk_wallet 1.0.0 version. Changes include small bug fixes and API improvements plus an improved algorithm for determining which transactions are in the current best "canonical" block chain. The new canonicalization algorithm processes the transaction graph in linear time versus the prior quadratic time algorithm.
Release numbering must follow Semantic Versioning. These steps assume the current master branch development version is v1.0.0-beta.5.
On the day of the feature freeze
Change the master branch to the next MINOR+1 version:
Ensure all alpha milestone issues and PRs closed, archive them on the project board.
Switch to the master branch.
Create a new PR branch called release/bump_dev_1.0.0_beta.6.
Create a "draft" release page and release notes comparing master commmit with prior tag v1.0.0-beta.5
Determine which crates need a major release bump and which only need a patch release by looking at the git log. cargo-semver-checks can also help with this cargo semver-checks --baseline-rev <last-tag>
Bump the bump_dev_1.0.0_beta.6 branch to the next development version.
Bump the modified crates versions in their Cargo.toml files. [update this list with only changed crates]
bdk_core
bdk_chain
bdk_bitcoind_rpc
bdk_electrum
bdk_esplora
bdk_file_store
bdk_testenv
bdk_wallet
The commit message should be: [update this list with only changed crates]
Bump bdk_wallet version to 1.0.0-beta.6
bdk_core to 0.4.0
bdk_chain to 0.21.0
bdk_bitcoind_rpc to 0.17.0
bdk_electrum to 0.20.0
bdk_esplora to 0.20.0
bdk_file_store to 0.18.0
bdk_testenv to 0.11.0
Summary
This is the final "beta" test release before a final
bdk_wallet
1.0.0 version. Changes include small bug fixes and API improvements plus an improved algorithm for determining which transactions are in the current best "canonical" block chain. The new canonicalization algorithm processes the transaction graph in linear time versus the prior quadratic time algorithm.Commit
606a2b0
Changelog
crates/chain/tests/common
totestenv
crate Refactor: Move transaction testing utilities fromcrates/chain/tests/common
totestenv
crate #1612ConfirmationTime
#1643load_with_params
fix(wallet): fix building change signers inload_with_params
#1662inner
method from KeychainTxOutIndex #1652bitcoin::constants::COINBASE_MATURITY
Usebitcoin::constants::COINBASE_MATURITY
#1727SyncResult
toSyncResponse
#1732rusqlite
impl Check time when persisting inrusqlite
impl #1730debug_assert!
onapply_update
#1734ChainPosition
#1733electrum-client
to 0.22.0 #1751esplora-client
to 0.11.0 #1746fetch_prev_txout
from querying coinbase transactions #1756O(n)
canonicalization algorithm IntroduceO(n)
canonicalization algorithm #1670O(n)
canonicalization algorithm #1670O(n)
canonicalization algorithm #1670O(n)
canonicalization algorithm #1670Checklist
Release numbering must follow Semantic Versioning. These steps assume the current
master
branch development version is v1.0.0-beta.5.On the day of the feature freeze
Change the
master
branch to the next MINOR+1 version:master
branch.release/bump_dev_1.0.0_beta.6
.v1.0.0-beta.5
cargo-semver-checks
can also help with thiscargo semver-checks --baseline-rev <last-tag>
bump_dev_1.0.0_beta.6
branch to the next development version.Bump the modified crates versions in their
Cargo.toml
files. [update this list with only changed crates]The commit message should be: [update this list with only changed crates]
release/bump_dev_1.0.0_beta.6
branch tomaster
. Bump bdk_wallet version to 1.0.0-beta.6 #1772On the day of the release
Tag and publish new release:
HEAD
commit in themaster
branch.git tag v1.0.0-beta.6 --sign -e
v1.0.0-beta.6
--sign
flag.git tag -v v1.0.0-beta.6
bitcoindevkit/bdk
repo.git push upstream --tag v1.0.0-beta.6
cargo publish -p <crate name>
Release 1.0.0-beta.6
.1.0.0
release check the "Pre-release" box.The text was updated successfully, but these errors were encountered: