Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update rust crate wasmtime to v29 #80

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 21, 2025

This PR contains the following updates:

Package Type Update Change
wasmtime dev-dependencies major 27.0.0 -> 29.0.0

Release Notes

bytecodealliance/wasmtime (wasmtime)

v29.0.1

Compare Source

29.0.1

Released 2025-01-21.

Fixed
  • Fix a missing increment in WASIp1-to-WASIp2 adapter which affected WASI
    configurations that have multiple preopened directories.
    #​10064

v29.0.0

Compare Source

29.0.0

Released 2025-01-20.

Added
  • Winch now supports epoch-based interruption.
    #​9737

  • Pulley, Wasmtime's WebAssembly interpreter, has seen quite a lot of progress
    and support fleshed out. It's still not 100% complete but should be about
    ready to start kicking the tires.
    #​9744

  • The Wasmtime CLI now supports a -Wextended-const flag to control whether the
    extended-const wasm proposal is enabled or not.
    #​9768

  • Work continues to progress on the AArch64 Winch backend, bringing it closer to
    completion.
    #​9762
    #​9767
    #​9751
    #​9784
    #​9781
    #​9792
    #​9787
    #​9798
    #​9850

  • Wasmtime now supports a "custom code publisher" which can be useful when
    Wasmtime doesn't have built-in support for a particular environment.
    #​9778

  • Configuration options have been added for wasmtime-wasi-http outgoing
    bodies.
    #​9800

  • Log prefixes can now be disabled for the wasmtime serve command.
    #​9821

  • A new WASMTIME_LOG_NO_CONTEXT environment variable was added to live
    alongside WASMTIME_LOG.
    #​9902

  • Release artifacts for aarch64-musl targets are now available.
    #​9934

Changed
  • Wasmtime libcalls now return whether a trap happened rather than raising a
    trap directly to better prepare for the Pulley interpreter and an eventual
    implementation of Wasm exception-handling.
    #​9710

  • Wasmtime will now use the Pulley interpreter by default on platforms that
    are not supported by Cranelift.
    #​9741

  • Demangling symbols in profiling and debugging has improved to handle failures
    to demangle C++ symbols.
    #​9756

  • WASI WIT files have been updated to 0.2.3.
    #​9807

  • Wasmtime's bindgen! macro in async mode no longer uses #[async_trait]
    an instead natively uses async fn in traits.
    #​9867

  • Floats are no longer canonicalized flowing into or out of components.
    #​9879

  • Instance methods are now translated to static methods in DWARF translation.
    #​9898

  • The C API now supports debug builtins for debugging guest code.
    #​9915

Fixed
  • The header file for wasmtime_instance_pre_instantiate in the C API has been
    fixed.
    #​9770

  • WebAssembly DWARF is more conservative in its GC pass during translation to
    native DWARF.
    #​9829

  • Debugging intrinsics are fixed on Linux to be exported now.
    #​9866

v28.0.1

Compare Source

28.0.1

Released 2025-01-14.

Fixed
  • Fixed deallocating async stacks when using Store::into_data.
    #​10009

v28.0.0

Compare Source

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

  • Linear memories now have a 32MiB guard region at the end instead of a 2GiB
    guard region by default.
    #​9606

  • Wasmtime will no longer validate dependencies between WebAssembly features,
    instead delegating this work to wasmparser's validator.
    #​9623

  • Cranelift's isle-in-source-tree feature has been re-worked as an environment
    variable.
    #​9633

  • Wasmtime's minimum supported Rust version is now 1.81.
    #​9692

  • Synthetic types in DWARF are now more efficiently represented.
    #​9700

  • Debug builtins on Windows are now exported correctly.
    #​9706

  • Documentation on Config now clarifies that defaults of some options may
    differ depending on the selected target or compiler depending on features
    supported.
    #​9705

  • Wasmtime's error-related types now all unconditionally implement the Error
    trait, even in #[no_std] mode.
    #​9702

Fixed
  • Field type matching for subtyping with wasm GC has been fixed.
    #​9724

  • Native unwind info generated for s390x has been fixed in the face of tail
    calls.
    #​9725


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 this update again.


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

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

Copy link
Contributor Author

renovate bot commented Jan 21, 2025

⚠️ 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 crates/code-generator/Cargo.toml --package [email protected] --precise 29.0.0
    Updating crates.io index
error: failed to select a version for the requirement `wasmtime = "^27.0.0"`
candidate versions found which didn't match: 29.0.0
location searched: crates.io index
required by package `wasmtime-wasi v27.0.0`
    ... which satisfies dependency `wasmtime-wasi = "^27.0.0"` (locked to 27.0.0) of package `code-generator v0.1.0 (/tmp/renovate/repos/github/ricora/ao/crates/code-generator)`

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants