Repository navigation
Bind browser SDK 0.0.6 assets to Core v0.0.11-rc.4 - #21
Merged
Merged
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.
Bind SDK 0.0.6 release exports, types and all verifier/writer WASM assets to the exact published Core v0.0.11-rc.4 tag, commit and checksums. Document the inherited rc.3 empty-cell regeneration requirement.
Keep checksum manifests consistent across Windows and Linux. CI rebuilds into a separate directory and checks every payload byte and all provenance except the build-host OS/architecture, with complete checksums verified on both sides. Actual host provenance remains recorded. Tag-lookup tests now also work under Git Bash.
Validation on Windows: 159 package tests, typecheck, standalone Go tests, release audit, asset checks, verifier vectors, all KZG/IPA writer profiles and retained/batch/Worker conformance, npm pack dry-run, and independent asset-hash verification passed. A fresh reviewer found no actionable issues. POSIX-only backend-gate unit tests and cross-host reproduction remain CI checks; the actual backend-isolation gate passed locally. This source change does not publish an npm version or SDK tag.