Repository navigation
discover: ship runtime-wasm-v0.16.2 in the execute panel - #188
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.
The /discover execute panel still served the v0.13.0 runtime.wasm (a254c161...). This swaps in the runtime-wasm-v0.16.2 release asset (runtime 0.16.2, bridge 1.1.0, sha256 b313b5c5c11291d9e9669125a0a9a77aa42a911b15d431a73e86b17c874e298c, verified against the release sidecar), updates the RUNTIME_WASM_DIGEST pin and sidecar, and updates the website-embedder Q&A and llms.txt that called this out as a lag.
Local: npm test 11 pass / 2 skipped (digest pin test included), astro build OK, Playwright 6/6. The known report.* embedding-chain failure at node 1 is unchanged with the new bytes.