chore(deps): bump the wasmtime-deps group with 2 updates#1078
chore(deps): bump the wasmtime-deps group with 2 updates#1078dependabot[bot] wants to merge 4 commits intomainfrom
Conversation
Bumps the wasmtime-deps group with 2 updates: [wasmtime](https://github.com/bytecodealliance/wasmtime) and [wasmtime-wasi](https://github.com/bytecodealliance/wasmtime). Updates `wasmtime` from 36.0.6 to 38.0.4 - [Release notes](https://github.com/bytecodealliance/wasmtime/releases) - [Changelog](https://github.com/bytecodealliance/wasmtime/blob/v38.0.4/RELEASES.md) - [Commits](bytecodealliance/wasmtime@v36.0.6...v38.0.4) Updates `wasmtime-wasi` from 36.0.6 to 38.0.4 - [Release notes](https://github.com/bytecodealliance/wasmtime/releases) - [Changelog](https://github.com/bytecodealliance/wasmtime/blob/v38.0.4/RELEASES.md) - [Commits](bytecodealliance/wasmtime@v36.0.6...v38.0.4) --- updated-dependencies: - dependency-name: wasmtime dependency-version: 38.0.4 dependency-type: direct:production update-type: version-update:semver-major dependency-group: wasmtime-deps - dependency-name: wasmtime-wasi dependency-version: 38.0.4 dependency-type: direct:production update-type: version-update:semver-major dependency-group: wasmtime-deps ... Signed-off-by: dependabot[bot] <support@github.com>
wasmtime 38.0.4 depends on cranelift 0.125.4 which requires rustc 1.88.0. Also bump wasmtime-wasi-http from 36.0.6 to 38.0.4 to avoid version conflicts, and update preview1 -> p1 import per wasmtime API changes. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Fix uninlined_format_args warnings triggered by the newer clippy in Rust 1.88.0 across the workspace. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Closing this PR because wasmtime 38.0.4 has multiple known security vulnerabilities with no fix available in the 38.x release series:
The current version (36.0.6) already has all these security fixes. Upgrading to 38.0.4 would regress on security. The The next safe upgrade target would be wasmtime 40.0.4+ or 41.0.4+ or 42.0.0+, which include patches for all three advisories. Additionally, wasmtime 38.0.4 requires bumping the Rust toolchain from 1.86.0 to 1.88.0 and includes breaking API changes ( A future dependabot PR bumping to wasmtime >= 40.0.4 would be the appropriate upgrade path. |
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
Bumps the wasmtime-deps group with 2 updates: wasmtime and wasmtime-wasi.
Updates
wasmtimefrom 36.0.6 to 38.0.4Release notes
Sourced from wasmtime's releases.
... (truncated)
Changelog
Sourced from wasmtime's changelog.
... (truncated)
Commits
4c22e15Release Wasmtime 38.0.4 (#12024)9ebb693[38.0.x] Prevent using shared memories withMemory(#12020)05566ccWork around naked-function-plus-LTO issue (#11960) (#11972)e7eb46bPin beta Rust used in CI (#11969)d9dc16bRelease Wasmtime 38.0.3 (#11934)c3d448cUse generic array-to-wasm trampolines for components (#11933)e8b8a72Fix release script (#11906) (#11914)b27d62cRelease Wasmtime 38.0.2 (#11903)7c142a6Attempt to use github immutable releases (#11902)aba7144Fix compatibility with the Go runtime on Windows for exceptions (#11892) (#11...Updates
wasmtime-wasifrom 36.0.6 to 38.0.4Release notes
Sourced from wasmtime-wasi's releases.
... (truncated)
Changelog
Sourced from wasmtime-wasi's changelog.
... (truncated)
Commits
4c22e15Release Wasmtime 38.0.4 (#12024)9ebb693[38.0.x] Prevent using shared memories withMemory(#12020)05566ccWork around naked-function-plus-LTO issue (#11960) (#11972)e7eb46bPin beta Rust used in CI (#11969)d9dc16bRelease Wasmtime 38.0.3 (#11934)c3d448cUse generic array-to-wasm trampolines for components (#11933)e8b8a72Fix release script (#11906) (#11914)b27d62cRelease Wasmtime 38.0.2 (#11903)7c142a6Attempt to use github immutable releases (#11902)aba7144Fix compatibility with the Go runtime on Windows for exceptions (#11892) (#11...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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions