Skip to content

Comments

chore(deps): bump wasmtime-wasi from 39.0.1 to 41.0.3#159

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/cargo/wasmtime-wasi-41.0.3
Open

chore(deps): bump wasmtime-wasi from 39.0.1 to 41.0.3#159
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/cargo/wasmtime-wasi-41.0.3

Conversation

@dependabot
Copy link
Contributor

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

Bumps wasmtime-wasi from 39.0.1 to 41.0.3.

Release notes

Sourced from wasmtime-wasi's releases.

v41.0.3

41.0.3

Released 2026-02-04.

Fixed

  • Fix an incorrect mid-end optimization rule that could cause a compiler panic due to mismatched types. #12504

v41.0.2

41.0.2

Released 2026-02-03.

Fixed

  • Reduce the dependencies of the wasmtime-internal-jit-icache-coherence crate. #12446

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

... (truncated)

Changelog

Sourced from wasmtime-wasi's changelog.

41.0.3

Released 2026-02-04.

Fixed

  • Fix an incorrect mid-end optimization rule that could cause a compiler panic due to mismatched types. #12504

41.0.2

Released 2026-02-03.

Fixed

  • Reduce the dependencies of the wasmtime-internal-jit-icache-coherence crate. #12446

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

... (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 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)

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

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Feb 9, 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: 49c9e8623a

ℹ️ 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 = "39.0.1", features = ["cache", "cranelift"] }
wasmtime-wasi = "39.0.1"
wasmtime-wasi = "41.0.3"

Choose a reason for hiding this comment

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

P1 Badge Align wasmtime version with wasmtime-wasi

Bumping wasmtime-wasi to 41.0.3 while keeping wasmtime at 39.0.1 will pull in two incompatible wasmtime versions. This crate uses wasmtime::Linker/Store directly (e.g., in crates/runtime/src/runtime.rs when calling p1::add_to_linker_sync), but the wasmtime-wasi API expects the 41.x wasmtime types, causing a type mismatch and build failure once the dependency graph resolves both versions. Update wasmtime to 41.0.3 (or keep wasmtime-wasi at 39.0.1) so the linker and wasi types come from the same crate version.

Useful? React with 👍 / 👎.

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