feat(toolkit): add patch inspection and verification#42
Draft
JimmyDaddy wants to merge 1 commit into
Draft
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
inspectPatch()andverifyPatch()APIs for Android, iOS, and WebWhy
The package could create and apply compatible patches, but consumers did not have a portable way to inspect patch metadata or verify restored output. The site also needed practical distribution utilities and an evidence-backed description of large-file limits.
Validation
yarn install --immutableyarn prepareyarn lintyarn typecheckyarn test --runInBandyarn test:native-operationsyarn test:webyarn test:web:browseryarn test:web:metroyarn test:packageyarn site:buildyarn site:testyarn site:test:browsernpm pack --dry-run --ignore-scripts --jsonyarn npm audit --all --recursiveMeasured limits
EWEBASSEMBLY; the checked-in baseline and roadmap record this as an unsupported boundary rather than a performance guaranteeEnvironment note
A fresh CocoaPods install was not run locally because the system Ruby is 3.0 while the repository requires Ruby 3.2 or newer. The existing workspace completed the New Architecture Simulator Release build successfully.