Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
f0rr0
marked this pull request as ready for review
October 6, 2026 10:38
This was referenced Oct 8, 2026
f0rr0
merged commit Oct 8, 2026
1ecbf86
into
f0rr0/wasmer-dependency-refresh-20261003
237 of 242 checks passed
f0rr0
added a commit
that referenced
this pull request
Oct 8, 2026
* build(wasix): upgrade embedded runtime to Wasmer 7.5 Refresh the coherent Wasmer/WASIX family, parser, Node-API bindings, and Rust build toolchain. Adapt upstream package metadata and regenerate affected dependency-license contracts. Linux core execution is verified. Keep the browser and Postmaster pins unchanged pending adapter and patch ports; the existing Windows LLVM AOT producer is not supported by upstream 7.5. * build: standardize on the minimum shared Rust toolchain Use Rust 1.96.0 for the workspace and both baseline container builders, with a common 1.96 minimum in maintained and generated Cargo packages. Let private workspace tools inherit the shared minimum. * feat(wasix): upgrade browser host to Wasmer SDK 0.19 * feat(wasix): integrate bundled Windows V8 engine and native caches (#255) * feat(wasix): integrate bundled Windows V8 engine and native caches * fix(release): plan embedded engine payloads before source acquisition * fix(ci): qualify Windows engine contracts before cache production * test(wasix): qualify the frozen Windows engine package closure * fix(wasix): remove LLVM inputs from Windows runtime qualification * fix(packaging): close transitive path dependency test sources * test(wasix): run installed Windows SDK against frozen AOT carriers * test(wasix): qualify the full extension lifecycle on Windows V8 * refactor(wasix): keep one Windows cache producer helper * refactor(wasix): name native value ownership explicitly * refactor(wasix): align engine qualification and producer conventions * fix(ci): prepare WASIX engine toolchains and lifecycle sources * fix(ci): execute selected WASIX engine tasks without base lookup * fix(wasix): extract Windows engine archive with a local path * fix(wasix): close installed engine qualification dependencies * fix(packaging): normalize native Windows Cargo file listings * fix(wasix): keep dependency resolution in native qualification * fix(ci): serialize WASIX server executable consumers * fix(wasix): split oversized Windows AOT Cargo payloads * fix(wasix): align qualification and maintainer workflows * perf(packaging): reuse validated Windows payload archives * fix(wasix): align engine patches and qualification inputs
This was referenced Oct 8, 2026
This branch was successfully deployed
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
1 participant
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.
Wasmer 7.5 no longer supports its LLVM backend on Windows. Keep WASIX and the Rust/Node SDK APIs and installation flow consistent across desktop hosts by delivering a bundled V8 engine and precompiled native caches on Windows. Linux and macOS retain LLVM loading; consumers receive the engine and guest artifacts through their normal SDK packages.
Validation:
Requiredat8db3bd8885c32a5ca546f9038fc04764ab56610b, including desktop WASIX hosts, installed Windows engine/SDK checks, and the packaged Node extension catalog.Qualifiedis intentionally skipped on PRs.Requiredatd684f94421dd9fee3dcc43ac5d03a5eaee25544b: 120 jobs passed, including all four desktop WASIX hosts, the installed Windows engine, baseline caches, Rust/npm package checks, and extension lifecycle tests. The first attempt stopped on transient GitHub HTTP 500 responses downloading pinned ICU data.Qualifiedremains intentionally skipped for this PR; publication requires qualification of the integrated main commit.This PR is stacked on #247, which is based on #218. A merge-tree check against main (
30dda9f47f5c13f338351611a2923ec5f781bcfe) has no textual conflicts. Before integration, restack the parents and use the existing release version synchronization for the five engine manifests and Cargo.lock: their versions are 0.3.1 on the upgrade base while main's runtime is 0.3.2. Publication still requires successful qualification on the integrated main commit.Deep-recursion SQL recovery is tracked in #265; Windows startup/runtime/package measurements are tracked in #266.