Release 1.0.0-alpha.6

[notmandatory]

Create a new minor release

Summary

This small bi-weekly release fixes TxBuilder to support setting explicit nSequence for foreign inputs, and adds a new option for Esplora APIs to include floating TxOuts in pudates for fee calculations.

Commit

50c549b

Changelog

Fixed

• TxBuilder now supports setting explicit nSequence for foreign inputs. tx_builder: Support setting explicit nSequence for foreign inputs #1316

Added

• New Option for Esplora APIs to include floating TxOuts in updates for fee calculation. feat(esplora): include previous TxOuts for fee calculation #1308

Checklist

Release numbering must follow Semantic Versioning. These steps assume the current master branch development version is 1.0.0-alpha.5.

On the day of the feature freeze

Change the master branch to the 1.0.0-alpha.6 version:

• Switch to the master branch.
• Create a new PR branch called bump_dev_1.0.0_alpha.6.
• Bump the bump_dev_1.0.0_alpha.6 branch to the next development MINOR+1 version.
  • Change the bdk Cargo.toml version value to 1.0.0-alpha.6.
  • Bump the other modified crates versions in their Cargo.toml files.
    • bdk_chain
    • bdk_bitciond_rpc
    • bdk_electrum
    • bdk_esplora
    • bdk_file_store
  • The commit message should be:

    Bump version to 1.0.0-alpha.6
    
    bdk_chain to 0.10.0
    bdk_bitcoind_rpc to 0.5.0
    bdk_electrum to 0.8.0
    bdk_esplora to 0.8.0
    bdk_file_store to 0.6.0
    

• Create PR and merge the bump_dev_1.0.0-alpha.6 branch to master. Bump bdk version to 1.0.0-alpha.6 #1347
  • Title PR "Bump bdk version to 1.0.0-alpha.6".

On the day of the release

Tag and publish new release:

• Add a tag to the HEAD commit in the master branch.
  • The tag name should be v1.0.0-alpha.6
  • The first line of the tag message should be "Release 1.0.0-alpha.6".
  • 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 repo.
• Publish all the updated crates to crates.io.
  • bdk_chain
  • bdk_bitciond_rpc
  • bdk_electrum
  • bdk_esplora
  • bdk_file_store
  • bdk
• Create the release on GitHub.
  • Go to "tags", click on the dots on the right and select "Create Release".
  • Set the title to Release 1.0.0-alpha.6.
  • 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 Nostr.
• Celebrate 🎉

[notmandatory]

@danielabrozzoni I added #1203 to this release, but if it looks like review is going to be too long I'll take it out.