Skip to content

Bump Wasmtime to v49.0.0 prerelease - #3710

Draft
spinframeworkbot wants to merge 3 commits into
mainfrom
bump-wasmtime/prerelease-49.0.0
Draft

Bump Wasmtime to v49.0.0 prerelease#3710
spinframeworkbot wants to merge 3 commits into
mainfrom
bump-wasmtime/prerelease-49.0.0

Conversation

@spinframeworkbot

Copy link
Copy Markdown
Collaborator

Bumps Wasmtime to v49.0.0 prerelease

spinframeworkbot and others added 2 commits September 5, 2026 12:01
Signed-off-by: spinframeworkbot <202838904+spinframeworkbot@users.noreply.github.com>
Signed-off-by: itowlson <ivan.towlson@fermyon.com>

@alexcrichton alexcrichton left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

lgtm, although if more is needed other than a Rust update in CI I can look more closely at the other changes too

Comment thread Cargo.toml
Comment on lines +207 to 210
wasmtime = { git = "https://github.com/bytecodealliance/wasmtime", branch = "release-49.0.0" }
wasmtime-wasi = { git = "https://github.com/bytecodealliance/wasmtime", branch = "release-49.0.0", features = ["p3"] }
wasmtime-wasi-http = { git = "https://github.com/bytecodealliance/wasmtime", branch = "release-49.0.0", features = ["p3", "component-model-async"] }
wit-component = "0.247.0"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I realize this is automation-generated but one possible tweak, now that this is the first release this is in effect, would be to use 49.0.0-rc.1 on crates.io which would avoid the need for git deps

Signed-off-by: itowlson <ivan.towlson@fermyon.com>
@itowlson

itowlson commented Sep 7, 2026

Copy link
Copy Markdown
Collaborator

I've re-run the tests in case of flakiness, but internal_http_p3_p2 (service chaining across P3 / P2 boundary, https://github.com/spinframework/spin/tree/main/tests/runtime-tests/tests/internal-http-p3-p2) seems to be failing consistently. (Both failed jobs are the same test, just different OSes.) My only changes were sync/async chores in the sockets stack, so if this is real then I think it is likely down to something in Wasmtime. Giving it one more for luck but I think this might need some @dicej / @alexcrichton love - thanks!

@alexcrichton

Copy link
Copy Markdown
Contributor

Definitely looks like a Wasmtime-side issue, I'll poke at it today

@alexcrichton

Copy link
Copy Markdown
Contributor

Ok I've attempted a draft fix for that issue at bytecodealliance/wasmtime#14302, will report back here when that's ready.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants