Bump secp256k1-sys version to 0.7.0 #549
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
8aea626 to
45beac7
Compare
Member
Author
|
@apoelstra I did #550 so that we can merge this PR, tag and release |
This was referenced Nov 30, 2022
Member
Member
Author
|
Lets do them both :) |
Collaborator
|
Actually, since this bumps |
Member
|
@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
apoelstra
approved these changes
Dec 12, 2022
Member
|
Tagged and published secp-sys. |
chain-forgexcr45
added a commit
to chain-forgexcr45/rust-secp256k1
that referenced
this pull request
Sep 28, 2025
…0.7.0 3fa24362723ad6d4694437082300d49d2b4edee3 Bump secp256k1-sys version to 0.7.0 (Tobin C. Harding) Pull request description: 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`) ### Notes I based this PR on: - https://github.com/rust-bitcoin/rust-secp256k1/pull/490/files - https://github.com/rust-bitcoin/rust-secp256k1/pull/457/files ACKs for top commit: apoelstra: ACK 3fa24362723ad6d4694437082300d49d2b4edee3 Tree-SHA512: cb16de633865f26613aa29479ac6a6299b1790a00372cca61173f09a753179fa1d619b91ca25ba5872f571d3d9372b46731f9d4b3e8050077ec3c73d583f54ce
william2332-limf
added a commit
to william2332-limf/rust-secp256k1
that referenced
this pull request
Oct 2, 2025
…0.7.0 3fa24362723ad6d4694437082300d49d2b4edee3 Bump secp256k1-sys version to 0.7.0 (Tobin C. Harding) Pull request description: 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`) ### Notes I based this PR on: - https://github.com/rust-bitcoin/rust-secp256k1/pull/490/files - https://github.com/rust-bitcoin/rust-secp256k1/pull/457/files ACKs for top commit: apoelstra: ACK 3fa24362723ad6d4694437082300d49d2b4edee3 Tree-SHA512: cb16de633865f26613aa29479ac6a6299b1790a00372cca61173f09a753179fa1d619b91ca25ba5872f571d3d9372b46731f9d4b3e8050077ec3c73d583f54ce
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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-sysv0.7.0 do:0_6_1->0_7_0, done mechanically (search and replace)secp256k1-syscrate 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: