From 2e0ca4fe05f03d94ebb0b173220de2749c9819bc Mon Sep 17 00:00:00 2001 From: Alekos Filini Date: Tue, 26 Jan 2021 09:34:14 -0500 Subject: [PATCH] Fix the crate version in `src/lib.rs` --- DEVELOPMENT_CYCLE.md | 21 +++++++++++---------- src/lib.rs | 2 +- 2 files changed, 12 insertions(+), 11 deletions(-) diff --git a/DEVELOPMENT_CYCLE.md b/DEVELOPMENT_CYCLE.md index 6d733fbd..16b859e9 100644 --- a/DEVELOPMENT_CYCLE.md +++ b/DEVELOPMENT_CYCLE.md @@ -32,13 +32,14 @@ Pre-`v1.0.0` our "major" releases only affect the "minor" semver value. Accordin - If it's a minor issue you can just fix it in the release branch, since it will be merged back to `master` eventually - For bigger issues you can fix them on `master` and then *cherry-pick* the commit to the release branch 6. Update the changelog with the new release version. -7. On release day, make a commit on the release branch to bump the version to `x.y.z`. The message should be "Bump version to x.y.z". -8. Add a tag to this commit. The tag name should be `vx.y.z` (for example `v0.5.0`), and the message "Release x.y.z". Make sure the tag is signed, for extra safety use the explicit `--sign` flag. -9. Push the new commits to the upstream release branch, wait for the CI to finish one last time. -10. Publish **all** the updated crates to crates.io. -11. Make a new commit to bump the version value to `x.y.(z+1)-dev`. The message should be "Bump version to x.y.(z+1)-dev". -12. Merge the release branch back into `master`. -13. Create the release on GitHub: go to "tags", click on the dots on the right and select "Create Release". Then set the title to `vx.y.z` and write down some brief release notes. -14. Make sure the new release shows up on crates.io and that the docs are built correctly on docs.rs. -15. Announce the release on Twitter, Discord and Telegram. -16. Celebrate :tada: +7. Update `src/lib.rs` with the new version (line ~59) +8. On release day, make a commit on the release branch to bump the version to `x.y.z`. The message should be "Bump version to x.y.z". +9. Add a tag to this commit. The tag name should be `vx.y.z` (for example `v0.5.0`), and the message "Release x.y.z". Make sure the tag is signed, for extra safety use the explicit `--sign` flag. +10. Push the new commits to the upstream release branch, wait for the CI to finish one last time. +11. Publish **all** the updated crates to crates.io. +12. Make a new commit to bump the version value to `x.y.(z+1)-dev`. The message should be "Bump version to x.y.(z+1)-dev". +13. Merge the release branch back into `master`. +14. Create the release on GitHub: go to "tags", click on the dots on the right and select "Create Release". Then set the title to `vx.y.z` and write down some brief release notes. +15. Make sure the new release shows up on crates.io and that the docs are built correctly on docs.rs. +16. Announce the release on Twitter, Discord and Telegram. +17. Celebrate :tada: diff --git a/src/lib.rs b/src/lib.rs index c3ac1ac0..d2737b47 100644 --- a/src/lib.rs +++ b/src/lib.rs @@ -56,7 +56,7 @@ //! interact with the bitcoin P2P network. //! //! ```toml -//! bdk = "0.2.0" +//! bdk = "0.3.0" //! ``` //! //! ## Sync the balance of a descriptor