Bump github.com/tetratelabs/wazero from 1.4.0 to 1.5.0 in /sdks

[dependabot]

Bumps github.com/tetratelabs/wazero from 1.4.0 to 1.5.0.

Release notes

Sourced from github.com/tetratelabs/wazero's releases.

v1.5.0

Hey, do you know what time is it? ⏰ Yes! Time for another wazero release! 🎉

Notably, as previously announced, this release drops support to Go 1.18. But you must be here for the goodies! Don't you worry, we have you covered: there's a whole lot of updates especially for you Emscripten fanatics!

Time flies when you are having fun: WasmCon 2023 is only a few days away (5-6 September). Remember, our very own @​evacchi will be there to talk about wazero, so if you are going to be there, don't be shy and say hi!

Improved Emscripten support

Contributor @​jerbob92 together with @​mathetake brought quite some improvements to our Emscripten support.

• There is now improved support to longjmp, especially useful to exception handling (tetratelabs/wazero#1611).
• We are now allowing a host function to make a nested invocation to another host function (#1626, #1636).
• We are exposing some new experimental APIs (tetratelabs/wazero#1637) to support a go implementation of Emscripten's Embind.

What is Embind? In @​jerbob92's words:

Embind allows developers to write C++ code and directly interact with that code from Javascript in the browser. It also allows to call Javascript methods directly from C++. [...] [The Wazero implementation] is trying to be a 1-on-1 implementation of the JS version in Emscripten so that the same codebase can be used for both Web and WASI WebAssembly builds.

Embind support lives in its own module and you can check it out at jerbob92/wazero-emscripten-embind!

Go Version Upgrade

As you may already know, we follow the Go support policy: i.e., we support each major Go release until there are two newer major releases: in v1.4.0 we added support to Go 1.21, while keeping support to Go 1.18 for a little while more. The time has come to say goodbye to Go 1.18: it's been an honor and a privilege, sir. 🫡

@​evacchi (tetratelabs/wazero#1622) and @​ncruces (tetratelabs/wazero#1620) upgraded the code paths that were relying on old workarounds or simply pointed to an older version.

Other Contributions

• While working on Emscripten support, @​jerbob92 discovered that looking up and calling a non-existing function may SIGILL on some platforms (#1621). Together with @​evacchi, they conducted some detective work and realized that the SIGILL was really due to a cross-compilation bug of a humble nil dereference panic @​mathetake released a workaround (tetratelabs/wazero#1623) while the bug is fixed upstream.

• @​mathetake updated our CI to align our test suites to their upstream (tetratelabs/wazero#1617, tetratelabs/wazero#1619, tetratelabs/wazero#1650).

• Some minor issues in path handling were fixed by @​evacchi in tetratelabs/wazero#1648

• We also welcome first-time contributor @​philippgille who made a fix to our README! (tetratelabs/wazero#1629)

Commits

• 9e4b8ea wazevo: passes: br_table, loads, select, store, and other spectests (#1658)
• 8d1fd50 wazevo: pass br, break-drop, and block spectests (#1657)
• f96f097 wazevo: pass memory_grow.wast (#1656)
• a5b30a5 wasi: fix symlink-related issues with path handling (#1648)
• 1223d11 wazevo: pass memory_size.wast (#1653)
• d0a3c2d wazevo: passes local_get.wast (#1652)
• 8c245b7 wazevo: passes address, binary, data, nop, etc spec tests (#1651)
• adaa417 wazevo: pass address.wast (#1649)
• 320d2aa ci: pins the version of wasi-testsuits (#1650)
• 967d8df Sets up spectest infra for wazevo (#1647)
• 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.

[github-actions]

This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the [email protected] list. Thank you for your contributions.

[github-actions]

This pull request has been closed due to lack of activity. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.