-
Notifications
You must be signed in to change notification settings - Fork 58
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
(MINOR) Update xmp_toolkit
to v1.7.1, remove Ring dependency, fix build errors
#407
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #407 +/- ##
=======================================
Coverage 79.93% 79.93%
=======================================
Files 80 79 -1
Lines 24240 24241 +1
=======================================
+ Hits 19377 19378 +1
Misses 4863 4863 ☔ View full report in Codecov by Sentry. |
xmp_toolkit
to v1.7.1 to resolve build issuexmp_toolkit
to v1.7.1, remove Ring dependency, fix build errors
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.
👍
bc7ef41
to
f147d80
Compare
xmp_toolkit
to v1.7.1, remove Ring dependency, fix build errorsxmp_toolkit
to v1.7.1, remove Ring dependency, fix build errors
ad73e2b
to
b8f99bf
Compare
Changes in this pull request
xmp_toolkit
to v1.7.1 to resolve a build issue stemming from a new version of thecc
crate (discussed in this issue).ring
since we were just using it for secure random number generation and it was causing a good deal of cross-compilation issues. This replaces it withCrypto.getRandomValues()
in Wasm and the ChaCha20Rng in systems not running OpenSSL.Updates the usage ofHad to pin toread_from
toread_from2
due to this change in theid3
crate.id3@=1.12.0
due to Rust 1.70 compatibility issues that undid this change.Checklist
TO DO
items (or similar) have been entered as GitHub issues and the link to that issue has been included in a comment.