chore(deps): update wasmtime to v23 (major)

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
wasmtime	workspace.dependencies	major	22.0.0 -> 23.0.0
wasmtime-wasi	workspace.dependencies	major	22.0.0 -> 23.0.0

---

Release Notes

bytecodealliance/wasmtime (wasmtime)

v23.0.1

Compare Source

23.0.1

Released 2024-07-22.

Fixed

• Fixed some issues when auto-publishing crates to crates.io.
  #​8986

v23.0.0

Compare Source

23.0.0

Released 2024-07-22.

Added

• Support for DWARF debugging information with native debuggers is now
  implemented for components.
  #​8693

• CLIF frontends can now define their own stack maps.
  #​8728
  #​8876

• Wasmtime now supports the custom-page-sizes proposal.
  #​8763

• This project now publishes a crate named
  wasi-preview1-component-adapter-provider which provides the WASIp1 adapters
  as constants in Rust code.
  #​8874

Changed

• Call hooks now have access to the full StoreContextMut<T>.
  #​8791

• Call hooks have been moved behind an off-by-default compile-time Cargo feature
  named call-hook.
  #​8795
  #​8808

• Wasmtime's minimum supported Rust version is now 1.77.0.
  #​8796

• Resumable traps have been removed from Cranelift.
  #​8809

• Traps are not GC safepoints any more in Cranelift.
  #​8810

• Support for Intel memory protection keys is now disabled by default at compile
  time and is gated behind a Cargo feature.
  #​8813

• Exports from components have been refactored and redesigned to support
  skipping name lookups at runtime where possible.
  #​8786

• Wasmtime's lookup of versioned component exports now takes semver into
  account in the same manner as imports.
  #​8830

• Wasmtime's guest profiler will now take samples at hostcall boundaries.
  #​8802

• Wasmtime's pooling allocator now by default allows 32-bit linear memories to
  grow to their full size of 4G.
  #​8849

• The size of WASI adapter binaries has been optimized.
  #​8858
  #​8859

• The wasmtime-wasi-http crate has been refactored to better match the
  wasmtime-wasi crate.
  #​8861

• Support for caching call_indirect sites has been removed.
  #​8881

• Wasmtime's x86_64 binary releases are now based on AlmaLinux 8 instead of
  CentOS 7.
  #​8892

Fixed

• An issue with generated .debug_loc sections for native debuggers has been
  fixed.
  #​8753

• Wasmtime's no_std build for riscv64 has been fixed.
  #​8770

• A bug related to lost Waker instances with async stdio streams has been
  fixed.
  #​8782

• Configuration of trappable_error_type has been improved in Wasmtime's
  bindgen! macro.
  #​8833

• Prints to stdout/stderr without a newline now work better with wasmtime serve.
  #​8877

• An issue with br_if and stack-related state has been fixed in Winch.
  #​8886

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 23.0.0
error: package ID specification `[email protected]` did not match any packages
Did you mean one of these?

  [email protected]

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.