Upgrade packages, replace mirage-crypto hashes with digestif #293
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ns of Term and remove dependency to mirage-crypto
mabiede
changed the title
mabiede
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @rgrinberg
When
mirage-crypto.1.0.0was released, they added an upper bound to many other packages, includingopium.This PR includes the following updates:
mirage-cryptowithdigestifbecausemirage-cryptodoesn't provide md5 and sha1 anymoreopium/src/app.mlmake fmt)make buildIt would be great to see a new version of
opiumin theopam-repository