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.

Sign up for GitHub

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

Jump to bottom

Release 0.27.1 #868

Closed
16 tasks done
notmandatory opened this issue Feb 15, 2023 · 2 comments
Closed
16 tasks done

Release 0.27.1 #868

notmandatory opened this issue Feb 15, 2023 · 2 comments
Assignees
@notmandatory
Labels
release Release related issue or PR
Milestone
Release 0.27.1

Comments

@notmandatory
Copy link
Member

notmandatory commented Feb 15, 2023 •
edited
Loading

Create a new patch release

Summary

Fixes RUSTSEC-2022-0090, this issue is only applicable if you are using the optional sqlite database feature.

Commit

7a8e660

Changelog

Changed

Checklist

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

On the day of the patch release

Change the master branch to the new PATCH+1 version:

  • Switch to the master branch.
  • Create a new PR branch called bump_dev_0_27_1.
  • Bump the bump_dev_0_27 branch to the next development PATCH+1 version.
    • Change the Cargo.toml version value to 0.27.1.
    • Update the CHANGELOG.md file.
    • The commit message should be "Bump version to 0.27.1".
  • Create PR and merge the bump_dev_0_27_1 branch to master.
    • Title PR "Bump version to 0.27.1".

Cherry-pick, tag and publish new PATCH+1 release:

  • Merge fix PRs to the master branch.
  • Git cherry-pick fix commits to the release/0.27 branch to be patched.
  • Verify fixes in release/0.27 branch.
  • Bump the release/0.27 branch to 0.27.1 version.
    • Change the Cargo.toml version value to 0.27.1.
    • The commit message should be "Bump version to 0.27.1".
  • Add a tag to the HEAD commit in the release/0.27 branch.
    • The tag name should be v0.27.1
    • The first line of the tag message should be "Release 0.27.1".
    • 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.1.
    • 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 notmandatory added the release Release related issue or PR label Feb 15, 2023
@notmandatory notmandatory added this to the Release 0.27.1 milestone Feb 15, 2023
@notmandatory notmandatory self-assigned this Feb 15, 2023
@notmandatory notmandatory mentioned this issue Feb 15, 2023
Merged
3 tasks
notmandatory added a commit that referenced this issue Feb 16, 2023
@notmandatory
Merge #869: Bump version to 0.27.1
843807b 
231a1fb Bump version to 0.27.1 (Steve Myers)

Pull request description:

  ### Description

  Bump dev version to 0.27.1.

  ### Notes to the reviewers

  This is in preparation for making a patch release and will be cherry picked to the release/0.27 branch. See #868.

  ### Changelog notice

  ### Checklists

  #### All Submissions:

  * [x] I've signed all my commits
  * [x] I followed the [contribution guidelines](https://github.com/bitcoindevkit/bdk/blob/master/CONTRIBUTING.md)
  * [x] I ran `cargo fmt` and `cargo clippy` before committing

Top commit has no ACKs.

Tree-SHA512: 7c791d221d95fb800c19b85c110a47f462b1c9ea7991dc1cf9bc5bb17d12b2dea9d1823d7f928ba06f09aaac36b1140610a29454857257f918124e0e0893fc4e
@notmandatory
Copy link
Member Author

notmandatory commented Feb 16, 2023 •
edited
Loading

Required downstream project updates:

@notmandatory
Copy link
Member Author

@rajarshimaitra and @thunderbiscuit I've renamed the next milestones for bdk-cli and bdk-ffi to 0.27.1 since they'll be based on this bdk 0.27.1 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@notmandatory notmandatory

Labels
release Release related issue or PR
Projects
BDK Maintenance
Archived in project
Milestone
Release 0.27.1
Development

No branches or pull requests
1 participant
@notmandatory