Repository navigation
deps: bind browser SDK to Core rc.4 - #16
Merged
Merged
Conversation
Advance the package asset binding to 0.0.3-rc.4 and rebuild verifier/KZG/IPA WASM with exact published Core commit and checksums. Linux conformance, JS tests, typecheck, asset checks and pack dry-run passed.
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.
Bind the browser package to the published MALT Core v0.0.10-rc.4 release at 0d7b166d58d1c2e21ead96de9c66968caf630374, update package metadata to 0.0.3-rc.4, and rebuild the verifier and four writer WASM profiles with matching checksums and provenance. The JS API and Core ABI are unchanged.
Validation: exact remote Core tag/release and module checksum audit; native Go tests; 152 JS tests; TypeScript checks; asset integrity; KZG/IPA verifier and writer conformance, batch receipts and Worker checks; npm pack --dry-run; clean-source WASM release archives and adversarial archive/provenance validation. A fresh independent reviewer reported no actionable findings.
This integrates source and assets for exact-commit downstream consumers. It does not publish a separate npm package or SDK tag.