Skip to content

Comments

Bump the cargo group across 2 directories with 1 update#390

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/cargo/cargo-9715246124
Open

Bump the cargo group across 2 directories with 1 update#390
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/cargo/cargo-9715246124

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 24, 2026

Bumps the cargo group with 1 update in the / directory: wasmtime.
Bumps the cargo group with 1 update in the /src/wasm_runtime directory: wasmtime.

Updates wasmtime from 36.0.5 to 36.0.6

Release notes

Sourced from wasmtime's releases.

v36.0.6

36.0.6

Released 2026-02-24.

Changed

  • Wasmtime's implementation of WASI now has the ability to limit resource consumption on behalf of the guest, such as host-allocated memory. This means that some behaviors previously allowed by Wasmtime can now disallowed, such as transferring excessive data from the guest to the host. Additionally calls to wasi:random/random.get-random-bytes, for example, can have limits in place to avoid allocating too much memory on the host. To preserve backwards-compatible behavior these limits are NOT set by default. Embedders must opt-in to configuring these knobs as appropriate for their embeddings. For more information on this see the related security advisory with further details on knobs added and what behaviors can be restricted. GHSA-852m-cvvp-9p4w

Fixed

  • Panics when adding too many headers to a wasi:http/types.fields has been resolved GHSA-243v-98vx-264h
Changelog

Sourced from wasmtime's changelog.

36.0.6

Released 2026-02-24.

Changed

  • Wasmtime's implementation of WASI now has the ability to limit resource consumption on behalf of the guest, such as host-allocated memory. This means that some behaviors previously allowed by Wasmtime can now disallowed, such as transferring excessive data from the guest to the host. Additionally calls to wasi:random/random.get-random-bytes, for example, can have limits in place to avoid allocating too much memory on the host. To preserve backwards-compatible behavior these limits are NOT set by default. Embedders must opt-in to configuring these knobs as appropriate for their embeddings. For more information on this see the related security advisory with further details on knobs added and what behaviors can be restricted. GHSA-852m-cvvp-9p4w

Fixed

  • Panics when adding too many headers to a wasi:http/types.fields has been resolved GHSA-243v-98vx-264h

Commits

Updates wasmtime from 36.0.5 to 36.0.6

Release notes

Sourced from wasmtime's releases.

v36.0.6

36.0.6

Released 2026-02-24.

Changed

  • Wasmtime's implementation of WASI now has the ability to limit resource consumption on behalf of the guest, such as host-allocated memory. This means that some behaviors previously allowed by Wasmtime can now disallowed, such as transferring excessive data from the guest to the host. Additionally calls to wasi:random/random.get-random-bytes, for example, can have limits in place to avoid allocating too much memory on the host. To preserve backwards-compatible behavior these limits are NOT set by default. Embedders must opt-in to configuring these knobs as appropriate for their embeddings. For more information on this see the related security advisory with further details on knobs added and what behaviors can be restricted. GHSA-852m-cvvp-9p4w

Fixed

  • Panics when adding too many headers to a wasi:http/types.fields has been resolved GHSA-243v-98vx-264h
Changelog

Sourced from wasmtime's changelog.

36.0.6

Released 2026-02-24.

Changed

  • Wasmtime's implementation of WASI now has the ability to limit resource consumption on behalf of the guest, such as host-allocated memory. This means that some behaviors previously allowed by Wasmtime can now disallowed, such as transferring excessive data from the guest to the host. Additionally calls to wasi:random/random.get-random-bytes, for example, can have limits in place to avoid allocating too much memory on the host. To preserve backwards-compatible behavior these limits are NOT set by default. Embedders must opt-in to configuring these knobs as appropriate for their embeddings. For more information on this see the related security advisory with further details on knobs added and what behaviors can be restricted. GHSA-852m-cvvp-9p4w

Fixed

  • Panics when adding too many headers to a wasi:http/types.fields has been resolved GHSA-243v-98vx-264h

Commits

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will 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 version will 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
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps the cargo group with 1 update in the / directory: [wasmtime](https://github.com/bytecodealliance/wasmtime).
Bumps the cargo group with 1 update in the /src/wasm_runtime directory: [wasmtime](https://github.com/bytecodealliance/wasmtime).


Updates `wasmtime` from 36.0.5 to 36.0.6
- [Release notes](https://github.com/bytecodealliance/wasmtime/releases)
- [Changelog](https://github.com/bytecodealliance/wasmtime/blob/v36.0.6/RELEASES.md)
- [Commits](bytecodealliance/wasmtime@v36.0.5...v36.0.6)

Updates `wasmtime` from 36.0.5 to 36.0.6
- [Release notes](https://github.com/bytecodealliance/wasmtime/releases)
- [Changelog](https://github.com/bytecodealliance/wasmtime/blob/v36.0.6/RELEASES.md)
- [Commits](bytecodealliance/wasmtime@v36.0.5...v36.0.6)

---
updated-dependencies:
- dependency-name: wasmtime
  dependency-version: 36.0.6
  dependency-type: direct:production
  dependency-group: cargo
- dependency-name: wasmtime
  dependency-version: 36.0.6
  dependency-type: direct:production
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Feb 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants