Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the adapter binaries cargo-component uses #370

Merged
merged 2 commits into from
Jan 21, 2025

Conversation

alexcrichton
Copy link
Member

This pulls in a fix for bytecodealliance/wasmtime#10058

@alexcrichton
Copy link
Member Author

The CI failure looks like it's due to the fact that the updated adapter has WASI 0.2.3 as the version where it previously had WASI 0.2.0. The version of Wasmtime used in CI wasn't old enough to have the forward-compatibility fix (CI used 22, the fix was in 23). I've confirmed that Wasmtime 23, as expected, works well with the new adapter.

I've gone ahead and pushed a commit that updates the version used in CI to Wasmtime 29.0.1 as well, the current latest release of Wasmtime.

@alexcrichton alexcrichton merged commit 241996c into bytecodealliance:main Jan 21, 2025
6 checks passed
@alexcrichton alexcrichton deleted the pull-in-update branch January 21, 2025 23:38
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