-
Couldn't load subscription status.
- Fork 305
Put back in deprecated context methods #872
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
Conversation
|
EDIT: I was off my head yesterday.
|
|
Tested using rust-bitcoin/rust-bitcoin#5169 |
|
EDIT: I was off my head yesterday.
|
9d7a33f to
0300949
Compare
During the removal of the context from the public API I brashly deleted a bunch of impls on the `Secp256k1` type when we could have just deprecated them. This means that when upgrading downstream crates the upgrade is way more painful than it is if we deprecate. Add back in the context impls. To do this I copied from `v0.31.1`. I'm not totally sure that there wasn't changes to this code in `master` but since we are explicitly doing this to help upgrade then it seems reasonable to do it like this. Add deprecated since 0.32 attributes because we are going to push this as a `0.32.0-beta.1` release. Sorry for the pain in reviewing this, I'm not entirely sure how you are supposed to convince yourself that the code is exactly as it was?
0300949 to
3815ee6
Compare
Typing `just update-lock-files` is boring, add an alias.
We just added the secp context methods back in (deprecated) to make upgrading easier. In preparation for release, bump the version, add a note in the changelog, and update the lock files.
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 243fdac; successfully ran local tests; awesome, thanks!
|
Tagged and published. |
During the removal of the context from the public API I brashly deleted a bunch of impls on the
Secp256k1type when we could have just deprecated them. This means that when upgrading downstream crates the upgrade is way more painful than it is if we deprecate.Add back in the context impls. Call through to the new API.