-
Notifications
You must be signed in to change notification settings - Fork 271
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.
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
Bump secp256k1-sys version to 0.7.0 #549
Bump secp256k1-sys version to 0.7.0 #549
Conversation
8aea626
to
45beac7
Compare
@apoelstra I did #550 so that we can merge this PR, tag and release |
Lets do them both :) |
Actually, since this bumps |
@tcharding ok, now I think this is the only thing blocking release of 0.25.0 :). But it needs rebase. |
We are ready to release a new minor version of `secp256k1-sys`, in order to do so we must make change the symbol names to reflect the new version as well as the usual changelog and version bump. In preparation for releasing `secp256k1-sys` v0.7.0 do: - Rename symbols to from `0_6_1` -> `0_7_0`, done mechanically (search and replace) - Add changes log notes - Bump `secp256k1-sys` crate version 0.6.1 -> 0.7.0, justified because we have added new public methods to various types (e.g., `PublicKey::cmp_fast_unstable`)
45beac7
to
3fa2436
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 3fa2436
Tagged and published secp-sys. |
We are ready to release a new minor version of
secp256k1-sys
, in order to do so we must make change the symbol names to reflect the new version as well as the usual changelog and version bump.In preparation for releasing
secp256k1-sys
v0.7.0 do:0_6_1
->0_7_0
, done mechanically (search and replace)secp256k1-sys
crate version 0.6.1 -> 0.7.0, justified because we have added new public methods to various types (e.g.,PublicKey::cmp_fast_unstable
)Notes
I based this PR on: