Skip to content
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

ripemd160 v0.9.0 #162

Merged
merged 1 commit into from
Jun 10, 2020
Merged

ripemd160 v0.9.0 #162

merged 1 commit into from
Jun 10, 2020

Conversation

tarcieri
Copy link
Member

Changed

  • Update to digest v0.9 release (#155)
  • Use new *Dirty traits from the digest crate (#153)
  • Bump block-buffer to v0.8 release (#151)
  • Rename *result* to finalize (#148)
  • Upgrade to Rust 2018 edition (#129)

@tarcieri
Copy link
Member Author

@newpavlov FYI, going to cut some releases of the higher priority hashes (at least for myself) then circle back on a final release of all of the rest of them

@tarcieri tarcieri merged commit fe7ff0d into master Jun 10, 2020
@tarcieri tarcieri deleted the ripemd160/v0.9.0 branch June 10, 2020 14:49
@newpavlov
Copy link
Member

Ok, right now I am working on updating to the new version of block-buffer, I don't think new releases should cause any merge conflicts. Though we will have to release patch updates right after v0.9.0 release.

@tarcieri
Copy link
Member Author

If you'd like to do that, I can just cut releases of the ones I immediately need, then we can do patch updates of just those rather than releasing all of them twice.

@newpavlov
Copy link
Member

I don't mind either, so if you would like to publish updates for other hashes right now, feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants