Bump wasmi from 0.40.0 to 0.51.1

[dependabot]

Bumps wasmi from 0.40.0 to 0.51.1.

Release notes

Sourced from wasmi's releases.

v0.51.1 - 2025-08-25

Fixed

• Fixed a bug that caused lazily compiled functions to be stuck at compiling when running out of fuel during translation. #1648

#1648: wasmi-labs/wasmi#1648

v0.51.0 - 2025-08-13

Final deprecations before Wasmi 1.0.

Changed

• Redesign the stack limits Config API. #1631
  • Deprecated the StackLimits type and Config::set_stack_limits method.
  • Deprecated the Config::cached_stacks method.
  • Added Config::set_{max_recursion_depth,min_stack_height,max_stack_height} methods.

#1631: wasmi-labs/wasmi#1631

v0.50.0 - 2025-08-11

This is supposedly the final release before Wasmi 1.0.0.

Added

• This version ships with an entirely new Wasm bytecode to Wasmi bytecode translator.
  • The new translator is ~5-10% faster than the old one.
  • Fuel-metering is no longer an afterthought and thus comes nearly for free.
  • The new codebase is much simpler to maintain and reason about.
  • Wasmi bytecode generated by the new translator shows similar performance as the old one.
  • The new translator provides a lot more information to Wasmi's optimizer which allows for new optimizations in upcoming Wasmi releases.
  • PRs: #1512 #1618
• Add lowerings for xor instructions when used in comparisons.
  • This reduced the number of Wasmi bytecode instructions by a whopping 20 which might have positive effects on execution performance due to decreased cache pressure.
  • PRs: #1625

Changed

• Removed Wasmi bytecode instructions that are no longer generated by the new translator.
  • This also reduces the number of Wasmi bytecode instructions by 8 which might have positive effects on execution performance due to decreased cache pressure.
  • PRs: #1623 #1624

Internal

• Remove some Wasmi dependencies.

... (truncated)

Changelog

Sourced from wasmi's changelog.

0.51.1 - 2025-08-25

Fixed

• Fixed a bug that caused lazily compiled functions to be stuck at compiling when running out of fuel during translation. #1648

#1648: wasmi-labs/wasmi#1648

0.51.0 - 2025-08-13

Changed

• Redesign the stack limits Config API. #1631
  • Deprecated the StackLimits type and Config::set_stack_limits method.
  • Deprecated the Config::cached_stacks method.
  • Added Config::set_{max_recursion_depth,min_stack_height,max_stack_height} methods.

#1631: wasmi-labs/wasmi#1631

0.50.0 - 2025-08-11

This is supposedly the final release before Wasmi 1.0.0.

Added

• This version ships with an entirely new Wasm bytecode to Wasmi bytecode translator.
  • The new translator is ~5-10% faster than the old one.
  • Fuel-metering is no longer an afterthought and thus comes nearly for free.
  • The new codebase is much simpler to maintain and reason about.
  • Wasmi bytecode generated by the new translator shows similar performance as the old one.
  • The new translator provides a lot more information to Wasmi's optimizer which allows for new optimizations in upcoming Wasmi releases.
  • PRs: #1512 #1618
• Add lowerings for xor instructions when used in comparisons.
  • This reduced the number of Wasmi bytecode instructions by a whopping 20 which might have positive effects on execution performance due to decreased cache pressure.
  • PRs: #1625

Changed

• Removed Wasmi bytecode instructions that are no longer generated by the new translator.
  • This also reduces the number of Wasmi bytecode instructions by 8 which might have positive effects on execution performance due to decreased cache pressure.
  • PRs: #1623 #1624

Internal

... (truncated)

Commits

• f3ade5a bump Wasmi crate versions to v0.51.1
• aa57d99 add changelog for v0.51.1
• c6b2cd5 Fix lazy translation when running into out of fuel (#1648)
• c329218 Prepare release for Wasmi v0.51.0 (#1633)
• 020a3f6 Redesign StackLimits API for Engine's config (#1631)
• 9037273 Prepare Wasmi v0.50.0 release (#1627)
• 6111401 Remove smallvec usage from ConstExpr::new method (#1626)
• c09b97d Remove i{32,64}.x[n]or[_br,_select] Wasmi IR instructions (#1625)
• 7399d70 Remove unused br_table Wasmi instruction variants (#1624)
• bf256e8 Remove Instruction::Copy{Span,Many} variants (#1623)
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[Robbepop]

@tomaka Side note on all the recent deprecations: I plan a v1.0 release for Wasmi so I wanted to remove all the APIs that either have a more efficient or general API replacement or are just underused. For example, the LinkerBuilder has a more general and equally (or better) efficient solution in the Instance::new API which is also supported by Wasmtime's API.

Furthermore, Wasmi's resumable calls API got more powerful since it is now possible to interrupt out-of-fuel cases. To reflect this there have been some renamings. That's it.

[tomaka]

@Robbepop My position so far is that, considering that all these API changes are mostly cosmetic, I'd rather wait for you to have a stable-enough API in order to upgrade.