elliptic-curve: apply digest API breaking changes#1859
Conversation
|
This is going to break tests. I'm not sure how to deal with it, I think I might suggest we add a: In digest to pass the hump. But anything that pulls both |
|
Shouldn't this pull in |
|
No it doesn't do that, and there is no easy way to do it either as it has dev-dependencies on sha2, which would in turn need a patch.crates-io |
|
So you're saying you want this merged even though it breaks the build? |
|
I actually don't know what's the best option here. The alternative is a release of digest with the buffering macros and then a release of sha1, sha2, hmac, pkcs5 and hkdf Then we will be able to merge this with the tests passing. |
|
Or split elliptic-curve integration tests in a crate outside the workspace in an unpublished crate that way we have more freedom to patch.crates-io and pull git dependencies. |
|
Why can't you just add Edit: seems to work: #1860 |
|
Note: I would also be a fan of adding a |
This would work for now, but the moment you bump the version of |
|
Well we wouldn't bump it until a release, when the |
|
Closing in favor of #1860 |
No description provided.