Shipped · DevOps and infrastructure

What WasmEdge/WasmEdge shipped

The public repository of Wasmedge · github.com/WasmEdge/WasmEdge

Written by FoxPlug from the repository's own releases; not affiliated with Wasmedge. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/WasmEdge/WasmEdge; Wasmedge did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for WasmEdge, free

Week of November 2, 2026

What shipped

Why it matters

These fixes correct WASI filesystem behavior so rename, mkdir, rmdir and path_link operate on symlinks as expected, and repair a C API copy function that could misorder arguments. The added path-resolution tests document existing symlink limits, and the AOT example now uses AOT mode. Contributors also see the disclosure requirement removed, simplifying pull requests.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: WASI rename/mkdir/rmdir/path_link no longer follow symlinks, wasm_val_vec_copy argument order fixed, symlink resolution tests added, AOT example updated with --run-mode=aot, and the AI disclosure requirement removed from contributor docs.

Post for LinkedIn

This week in WasmEdge: WASI path_rename, path_create_directory, path_remove_directory and path_link now resolve paths without following symlinks, so they act on the link itself. wasm_val_vec_copy had its argument order corrected and no longer reads uninitialized values. New tests cover symlink resolution, including chain limits and.. escapes. The AOT example now passes --run-mode=aot, and the Assisted-by disclosure requirement was removed from contributing docs and the PR template.

Week of October 26, 2026

What shipped

Why it matters

Wide arithmetic instructions are now type-checked by the validator, so programs using them get checked operands and results rather than passing through. WASI-Crypto has substantially more of its previously unimplemented API surface filled in, including the secrets manager and key management. The other changes are build and CI work that keeps wasm_bpf tests and the GCC 9 build passing and makes cache and Dependabot handling more predictable.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: the AOT cache formats its hash name directly and common/hexstr is removed; the validator now type-checks i64.add128, i64.sub128, i64.mul_wide_s and i64.mul_wide_u; WASI-Crypto gets a secrets manager, key management and more completed APIs; and CI fixes unbreak the wasm

Post for LinkedIn

What shipped this week in WasmEdge. The AOT cache now formats its hash name in lib/aot/cache.cpp and the common/hexstr helpers are removed entirely. The validator now checks operand and result types for i64.add128, i64.sub128, i64.mul_wide_s and i64.mul_wide_u, with 14 explicit validator cases and proposal checks kept in the loader. WASI-Crypto gains a secrets manager and key management, and a significant portion of previously unimplemented APIs across asymmetric and symmetric cryptography, key exchange and KDF state handling are completed or updated. On the build side, three CI breakages on master are fixed, covering the wasm_bpf tests, the GCC 9 build and Dependabot coverage uploads. The sccache server now starts up front with a fall back to the plain compiler, and Dependabot groups gith

Week of October 19, 2026

What shipped

Why it matters

This week's release of 0.18.1 brings validator fixes that prevent oversized allocations and accept/reject the right modules, plus restored CAPI symbols so applications built against 0.17.x load with the 0.18 library. AOT tail calls to imported functions and guarded 64-bit table error reporting affect compiled and interpreted execution. The remaining fixes harden parsing and type matching against malformed or edge-case inputs.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

WasmEdge 0.18.1 is out: bounded array.new_fixed validation, restored 0.17 CAPI symbols, br_table fix after unreachable, uint128 shift guards, AOT tail calls to imports, and a parse hang fix. Component-model spec tests updated too.

Post for LinkedIn

WasmEdge 0.18.1 is released. It bounds the validator's array.new_fixed operand check so a huge count fails validation without allocating gigabytes, and restores the backward-compatible WasmEdge_ModuleInstanceAdd symbols so applications linked against 0.17.x load with the 0.18 library. Other fixes this week include keeping br_table operand types after unreachable, guarding uint128 bitwise shifts, lowering return_call to imported functions as a native tail call in AOT, and preventing a uint32 overflow that made the parse tool hang on malformed name sections. The component-model loader and validator were also updated to the current spec and its tests to the wasm-core-20261019 tag.

Week of September 28, 2026

What shipped

Why it matters

Three stable and pre-release versions shipped this week, with significant improvements to component model support, call stack limits for spec compliance, and upstream dependency upgrades. Bug fixes address input validation, platform-specific socket handling, and type checking in the validator.

Changelog entry

Week of September 21, 2026

What shipped

Why it matters

This week includes critical stability fixes for stack overflow handling and memory access validation, along with platform-specific improvements for Windows socket handling and WASI polling. The pre-release candidate brings together fixes for edge cases in atomic operations, validator error reporting, and proper error mapping across platforms.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

0.17.2-rc.4 is out. Notable fixes: bounded recursion to prevent OOM, correct atomic.notify access width, Windows socket error mapping, and poll_oneoff timeout handling.

Post for LinkedIn

WasmEdge 0.17.2-rc.4 addresses critical stability improvements. The release bounds interpreter recursion to 8 MiB to prevent unbounded memory growth, fixes atomic memory operations to use correct access widths, improves Windows platform support with proper socket error mapping, and corrects WASI polling behavior for timeouts and edge cases.

Week of September 14, 2026

What shipped

Changelog entry

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-10.

Is this your repo? Ask us to remove this page.