Skip to content

Release 0.27.2 #891

@notmandatory

Description

@notmandatory

Create a new patch release

Summary

Disable default-features for rust-bitcoin and rust-miniscript dependencies, and for rust-esplora-client optional dependency.

Commit

de46a51

Changelog

Changed

Checklist

Release numbering must follow Semantic Versioning. These steps assume the current release/0.27
branch maintenace version is 0.27.1.

On the day of the patch release

Change the release/0.27 branch to the new PATCH+1 version:

  • Switch to the release/0.27 branch.
  • Create a new PR branch called bump_dev_0_27_2.
  • Bump the bump_dev_0_27_2 branch to the next development PATCH+1 version.
    • Change the Cargo.toml version value to 0.27.2.
    • Update the CHANGELOG.md file.
    • The commit message should be "Bump version to 0.27.2".
  • Create PR and merge the bump_dev_0_27_2 branch to release/0.27.
    • Title PR "Bump version to 0.27.2".

Cherry-pick or make new PRs on master, tag and publish new PATCH+1 release:

  • Merge fix PRs to the master branch.
    Set bitcoin, miniscript default-features = false, bump esplora-client version to 0.4 #893
  • Verify fixes in release branch.
  • Add a tag to the HEAD commit in the release/0.27 branch.
    • The tag name should be v0.27.2
    • The first line of the tag message should be "Release 0.27.2".
    • 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.
  • Create the release on GitHub.
    • Go to "tags", click on the dots on the right and select "Create Release".
    • Set the title to Release 0.27.2.
    • 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 🎉

Metadata

Metadata

Assignees

Labels

releaseRelease related issue or PR

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions