-
Notifications
You must be signed in to change notification settings - Fork 152
Release 9.0.0 #488
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
Release 9.0.0 #488
Conversation
sanket1729
commented
Nov 5, 2022
•
edited
Loading
edited
- Cleanup some pkh code in satisfaction
- Fixes We should not be running pkh logic through rawpkh #483
- Fixes another bug dealing with dissatisfaction of thresh inside pkh
- Adds example test vector from discussions
- release 9.0.0 with above fixes
Earlier, we only implemented `expr_raw_pkh` which was used as shortcut for c:expr_raw_pk_h. Note the inclusion of additional _
psbts where we needed to dissatisfy pkh did not work properly as we did not implement the mapping pkh->pk required for dissatisfaction of pkh fragment. We now look for this mapping in bip32 derivation field of psbt. Our update_utxo_from_descriptor API correctly procesess these fields.
Same example as posted in discussions
262049b
to
7e1a7a0
Compare
I'm not sure that we can change the |
Changing the signature of |
All changes in 7e1a7a0 look good to me, but they're all API-breaking and I think we need to release 9.0.0 with them. |
All of the changes are related to the raw APIs. I was thinking we can just
justify them as a bug fix instead of major release?
Thinking from a software sense, it makes sense to call it a breaking
change.
…On Mon, Nov 7, 2022, 2:03 PM Andrew Poelstra ***@***.***> wrote:
All changes in 7e1a7a0
<7e1a7a0>
look good to me, but they're all API-breaking and I think we need to
release 9.0.0 with them.
—
Reply to this email directly, view it on GitHub
<#488 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUQEOIJFIAKIEGDXKS7RELWHF4E3ANCNFSM6AAAAAARX3MG4E>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
@apoelstra what is expected date for the next release if the fix goes with it? |
@engenegr, you can expect a new release early next week. |
7e1a7a0
to
01a2b97
Compare
Changed to release 9.0.0 |
@sanket1729 you did not change the actual commit to 9.0.0! |
@apoelstra , lol. Good catch. I think you mean Cargo.toml file? |
01a2b97
to
a113e35
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 a113e35
Tagged & published |