fix(security/augurs-prophet): update wasmtime crates to v48 - #539
Merged
Conversation
…e-wasi-io to v48 Bumps all three wasmtime crates in lockstep from 42 to 48, resolving the wasmtime (medium) and wasmtime-wasi (high) security advisories flagged by Renovate in #508 and #509. Renovate raised these as separate PRs bumping one crate at a time, which is impossible: wasmtime, wasmtime-wasi and wasmtime-wasi-io must share the same major version, so each single-crate bump failed to compile with a version mismatch. Bumping all three together to the latest common release (48.0.0) satisfies both advisories and requires no source changes. Supersedes #508 and #509. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
wildum
approved these changes
Aug 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps
wasmtime,wasmtime-wasi, andwasmtime-wasi-ioinaugurs-prophetfrom 42 to 48 in lockstep, resolving both security advisories Renovate flagged:wasmtimeto v46 (medium) [security]wasmtime-wasito v45 (high) [security]Why one PR instead of two
These three crates must share the same major version. Renovate raised the advisories as separate PRs each bumping a single crate, which cannot compile — e.g.
wasmtime46 againstwasmtime-wasi42 fails withadd_to_linker_sync/IoView::tabletype-mismatch errors. Bumping all three together to the latest common release (48.0.0) satisfies both advisories and, as it happens, needs no source changes — the earlier CI failures were purely the version mismatch.Supersedes #508 and #509 (close both once this merges).
Testing
All run locally with
--all-features(matching CI):cargo check --all-targets --all-features✅just test-all→ 180/180 pass (incl.wasmstan,wasmstan_nans) ✅cargo clippy --all-features --all-targets -- -D warnings✅Note: wasmtime 48 raises the effective MSRV to Rust 1.95; CI builds on stable (currently 1.98) so this is fine.
🤖 Generated with Claude Code