-
Couldn't load subscription status.
- Fork 100
fix: bmff update manifest support #1284
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
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1284 +/- ##
==========================================
+ Coverage 78.04% 78.22% +0.18%
==========================================
Files 150 150
Lines 38354 38616 +262
==========================================
+ Hits 29933 30209 +276
+ Misses 8421 8407 -14 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
Looks good to me, just a few questions. Clever design by the spec too.
…ff_update_manifest
|
Clippy seems unhappy - not sure if this is due to the Rust update or not (I think not, since it ran after the new Rust version happened?). |
Make sure we always recurse ingredient certs
Changes in this pull request
This change add support for C2PA 2.2 changes to how we handle update manifests in for BMFF bases assest.
Checklist
TO DOitems (or similar) have been entered as GitHub issues and the link to that issue has been included in a comment.