Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 2, 2026

Bumps wasmtime from 39.0.1 to 41.0.1.

Release notes

Sourced from wasmtime's releases.

v41.0.1

41.0.1

Released 2026-01-26.

Fixed

  • Fixed a bug in lowering of f64.copysign on x86-64 whereby when combined with an f64.load, the resulting machine code could read 16 bytes rather than 8 bytes. This could result in a segfault when Wasmtime is configured without signals-based traps.

v41.0.0

41.0.0

Released 2026-01-20.

Added

  • Support for {Future,Stream}Any in the component model has improved. #12142

  • Wasmtime has initial support for breakpoints and single-stepping with the debug feature for guest programs. #12133

  • Wasmtime has begun adding a new Error type which is similar to anyhow::Error but supports gracefully handling OOM. Wasmtime still uses anyhow::Error but this will change in the future to wasmtime::Error which will be a distinct type. #12163

  • An initial top-level crate for async-debugging guest programs has been added. #12183

Changed

  • Cranelift now optimizes redundant select + icmp instructions. #12135

  • Synchronous component model functions can no longer block before returning. This implements a change in the upstream specification to the upcoming async support in the component model which places stricter restrictions on non-async functions and their ability to perform blocking operations. #12043

  • Frame iteration in debug mode now visits all activations which enables seeing all frames from recursive wasm calls. #12176

... (truncated)

Changelog

Sourced from wasmtime's changelog.

41.0.1

Released 2026-01-26.

Fixed

  • Fixed a bug in lowering of f64.copysign on x86-64 whereby when combined with an f64.load, the resulting machine code could read 16 bytes rather than 8 bytes. This could result in a segfault when Wasmtime is configured without signals-based traps.

41.0.0

Released 2026-01-20.

Added

  • Support for {Future,Stream}Any in the component model has improved. #12142

  • Wasmtime has initial support for breakpoints and single-stepping with the debug feature for guest programs. #12133

  • Wasmtime has begun adding a new Error type which is similar to anyhow::Error but supports gracefully handling OOM. Wasmtime still uses anyhow::Error but this will change in the future to wasmtime::Error which will be a distinct type. #12163

  • An initial top-level crate for async-debugging guest programs has been added. #12183

Changed

  • Cranelift now optimizes redundant select + icmp instructions. #12135

  • Synchronous component model functions can no longer block before returning. This implements a change in the upstream specification to the upcoming async support in the component model which places stricter restrictions on non-async functions and their ability to perform blocking operations. #12043

  • Frame iteration in debug mode now visits all activations which enables seeing all frames from recursive wasm calls. #12176

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Feb 2, 2026
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0c9364dd72

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines 31 to 32
wasmtime = { version = "41.0.1", features = ["cache", "cranelift"] }
wasmtime-wasi = "39.0.1"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Align wasmtime-wasi version with wasmtime

The runtime crate now depends on wasmtime = 41.0.1 while keeping wasmtime-wasi = 39.0.1. wasmtime-wasi re-exports/accepts wasmtime types (e.g., WasiCtxBuilder and linker helpers), and the runtime code uses wasmtime::{Engine, Linker, Store} alongside wasmtime_wasi APIs (crates/runtime/src/runtime.rs), so Cargo will compile two different wasmtime versions and the types will not unify. That yields compile-time type mismatches when passing a 41.x Store/Linker into 39.x wasmtime-wasi APIs. Bumping wasmtime-wasi to the matching 41.x line (or pinning both to 39.x) avoids the build break.

Useful? React with 👍 / 👎.

Bumps [wasmtime](https://github.com/bytecodealliance/wasmtime) from 39.0.1 to 41.0.1.
- [Release notes](https://github.com/bytecodealliance/wasmtime/releases)
- [Changelog](https://github.com/bytecodealliance/wasmtime/blob/v41.0.1/RELEASES.md)
- [Commits](bytecodealliance/wasmtime@v39.0.1...v41.0.1)

---
updated-dependencies:
- dependency-name: wasmtime
  dependency-version: 41.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/cargo/wasmtime-41.0.1 branch from 0c9364d to 048b0dd Compare February 3, 2026 02:07
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Feb 9, 2026

Superseded by #160.

@dependabot dependabot bot closed this Feb 9, 2026
@dependabot dependabot bot deleted the dependabot/cargo/wasmtime-41.0.1 branch February 9, 2026 03:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants