chore(deps): update wasmtime requirement from 27 to 28

[dependabot]

Updates the requirements on wasmtime to permit the latest version.

Release notes

Sourced from wasmtime's releases.

v28.0.0

28.0.0

Released 2024-12-20.

Added

• The ISLE DSL used for Cranelift now has a first-class bool type. #9593

• Cranelift now supports a new single-pass register allocator designed for compile-time performance (unlike the current default which is optimized for runtime-of-generated-code performance). #9611

• The wasmtime crate now natively supports the wasm-wave crate and its encoding of component value types. #8872

• A Module can now be created from an already-open file. #9571

• A new default-enabled crate feature, signals-based-traps, has been added to the wasmtime crate. When disabled then runtime signal handling is not required by the host. This is intended to help with future effort to port Wasmtime to more platforms. #9614

• Linear memories may now be backed by malloc in certain conditions when guard pages are disabled, for example. #9614 #9634

• Wasmtime's async feature no longer requires std. #9689

• The buffer and budget capacity of OutgoingBody in wasmtime-wasi-http are now configurable. #9670

Changed

• Wasmtime's external and internal distinction of "static" and "dynamic" memories has been refactored and reworded. All options are preserved but exported under different names with improved documentation about how they all interact with one another. (and everything should be easier to understand) #9545

• Each Store<T> now caches a single fiber stack in async mode to avoid allocating/deallocating if the store is used multiple times.

... (truncated)

Changelog

Sourced from wasmtime's changelog.

28.0.0

Released 2024-12-20.

Added

• The ISLE DSL used for Cranelift now has a first-class bool type. #9593

• Cranelift now supports a new single-pass register allocator designed for compile-time performance (unlike the current default which is optimized for runtime-of-generated-code performance). #9611

• The wasmtime crate now natively supports the wasm-wave crate and its encoding of component value types. #8872

• A Module can now be created from an already-open file. #9571

• A new default-enabled crate feature, signals-based-traps, has been added to the wasmtime crate. When disabled then runtime signal handling is not required by the host. This is intended to help with future effort to port Wasmtime to more platforms. #9614

• Linear memories may now be backed by malloc in certain conditions when guard pages are disabled, for example. #9614 #9634

• Wasmtime's async feature no longer requires std. #9689

• The buffer and budget capacity of OutgoingBody in wasmtime-wasi-http are now configurable. #9670

Changed

• Wasmtime's external and internal distinction of "static" and "dynamic" memories has been refactored and reworded. All options are preserved but exported under different names with improved documentation about how they all interact with one another. (and everything should be easier to understand) #9545

• Each Store<T> now caches a single fiber stack in async mode to avoid allocating/deallocating if the store is used multiple times. #9604

... (truncated)

Commits

• 2e584e8 Release Wasmtime 28.0.0 (#9876)
• edce721 Add release notes (#9771)
• d1ff945 wasi-http: make the buffer and budget capacity of the OutgoingBody writer con...
• abcd6ac Port wasmtime-fiber to no_std and allow async feature in no_std Wasmtim...
• 7ef8f2e winch: Improve frame handling (#9708)
• f40e53e Add basic pulley disassembly support to clif-util (#9721)
• 350a6e2 pulley: Fill out more bits and pieces of stack allocation (#9718)
• 94da012 Update clang-format to LLVM 18 (#9729)
• da7c53b winch: Prefer using Context::without for fuel checks (#9709)
• 06103f7 Update build/test images to Ubuntu 24.04 (#9728)
• Additional commits viewable in compare view

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.