Skip to content

feat(toolkit): add patch inspection and verification#42

Draft
JimmyDaddy wants to merge 1 commit into
mainfrom
feat/toolkit-utilities-and-metadata-api
Draft

feat(toolkit): add patch inspection and verification#42
JimmyDaddy wants to merge 1 commit into
mainfrom
feat/toolkit-utilities-and-metadata-api

Conversation

@JimmyDaddy

Copy link
Copy Markdown
Owner

Summary

  • add cross-platform inspectPatch() and verifyPatch() APIs for Android, iOS, and Web
  • add native runtime assertions for metadata, verification, malformed patches, mismatches, and resource limits
  • expand the Binary Patch Toolkit with integrity manifests, transfer-savings estimates, and bilingual error diagnostics
  • add 16/64/128 MiB isolated-process benchmarks and a bilingual v0.4 large-file/progress/streaming roadmap
  • update README, API/platform/development docs, package consumer coverage, and GitHub Pages Actions

Why

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 --immutable
  • yarn prepare
  • yarn lint
  • yarn typecheck
  • yarn test --runInBand
  • yarn test:native-operations
  • yarn test:web
  • yarn test:web:browser
  • yarn test:web:metro
  • yarn test:package
  • yarn site:build
  • yarn site:test
  • yarn site:test:browser
  • npm pack --dry-run --ignore-scripts --json
  • yarn npm audit --all --recursive
  • Android New Architecture Codegen and Release Kotlin compilation
  • iOS New Architecture Simulator Release build

Measured limits

  • native 16/64/128 MiB samples completed; the 128 MiB sample peaked around 2.37 GiB RSS
  • Web 16/64 MiB samples completed; the 64 MiB sample peaked around 2.09 GiB RSS
  • Web 128 MiB currently returns EWEBASSEMBLY; the checked-in baseline and roadmap record this as an unsupported boundary rather than a performance guarantee

Environment 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.

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.

1 participant