Skip to content

Conversation

alexcrichton
Copy link
Contributor

This commit updates Wasmtime from 35 to 36 to keep up-to-date with the latest release. This came with a number of refactors required to how WASI traits are handled in a few locations, but nothing major.

@alexcrichton
Copy link
Contributor Author

I'm starting this as a draft because bytecodealliance/wasmtime#11474 will be required to get merged/released. In the meantime I'd like to get a green bill of health on CI here to confirm.

@alexcrichton
Copy link
Contributor Author

Current plan is to do a 36.0.1 release of Wasmtime tomorrow at which point I'll un-draft this and fix the DCO thing to which I always forget about...

@alexcrichton alexcrichton force-pushed the wasmtime36 branch 2 times, most recently from 5686999 to 129c0ee Compare August 21, 2025 18:15
@alexcrichton alexcrichton marked this pull request as ready for review August 21, 2025 18:15
@alexcrichton alexcrichton changed the title Update to Wasmtime 36.0.0 Update to Wasmtime 36.0.1 Aug 21, 2025
@alexcrichton
Copy link
Contributor Author

Ok Wasmtime 36.0.1 is out and this should be ready to go (yay!)

This commit updates Wasmtime from 35 to 36 to keep up-to-date with the
latest release. This came with a number of refactors required to how
WASI traits are handled in a few locations, but nothing major.

Signed-off-by: Alex Crichton <alex@alexcrichton.com>
Copy link
Collaborator

@rylev rylev left a comment

Choose a reason for hiding this comment

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

🎉

@rylev rylev merged commit f51829e into spinframework:main Aug 22, 2025
17 checks passed
@alexcrichton alexcrichton deleted the wasmtime36 branch August 22, 2025 16:32
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.

2 participants