Release tracking PR: v0.32.0-beta.0
#843
Conversation
Based on the release tracking PR rust-bitcoin/rust-secp256k1#843 Just do the build errors, lint warnings done next.
Based on the release tracking PR rust-bitcoin/rust-secp256k1#843 Just do the build errors, lint warnings done next.
tcharding
force-pushed
the
push-ukmxqukmpvxw
branch
from
7124c05 to
6753b76
Compare
|
The only thing blocking this is that I would like to move the I wouldn't mind any further API improvements but let's not block this release over it. |
CHANGELOG.md
Outdated
| * #811 | ||
| * #794 | ||
| * #797 | ||
| * #798 | ||
| * #802 | ||
| * #803 | ||
| * #805 |
There was a problem hiding this comment.
All of the other PRs in this changelog diff have links, why these don't?
There was a problem hiding this comment.
Ah yes, thanks man, nice one.
|
@tcharding seems we've lost a bit of momentum here. Wanna just cut a RC (or a beta, I guess, since we know we have more changes to do) with what we've got? |
|
Steven would like to stop using a git dep in ark (git deps in Cargo have terrible interactions with Nix) and I would like to practice using this new API in p2c-s2c. |
|
Shall we get #858 in first? |
In preparation for release add a changelog entry, bump the version, and update the lock files.
tcharding
force-pushed
the
push-ukmxqukmpvxw
branch
from
6753b76 to
fc57f9d
Compare
tcharding
changed the title
v0.32.0v0.32.0-beta.0
Based on the release tracking PR rust-bitcoin/rust-secp256k1#843 Just do the build errors, lint warnings done next.
Based on the release tracking PR rust-bitcoin/rust-secp256k1#843 Just do the build errors, lint warnings done next.
|
Lets leave #858 out and get this released eh? |
|
We are good to go here, right? |
Based on the release tracking PR rust-bitcoin/rust-secp256k1#843 Just do the build errors, lint warnings done next.
|
Yes please 🙏 |
|
Yes, sorry, I've just been backlogged this week. |
|
omfg, I typed "863" instead of "843" when queuing this for testing. Sorry, it's in the queue now. Two things in front of it. Should be an hour or two. |
|
Crap. There were FFI changes associated with this. @tcharding we also need to release a beta version of secp256k1-sys. Really frustrating that cargo doesn't flag this kind of thing until you actually try to publish.. |
|
Neither tagged nor published. |
4 participants
In preparation for release add a changelog entry, bump the version, and update the lock files.