Skip to content

deps: updates wazero to v1.7.0 #3267

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

Closed
wants to merge 2 commits into from

Conversation

evacchi
Copy link

@evacchi evacchi commented Mar 12, 2024

This will update wazero to v1.7.0. The v1.7.0 release marks a milestone in the wazero project, replacing our old compiler architecture with a new optimizing compiler backend.. It also introduces experimental support to the thread spec.

We will officially announce the final v1.7.0 release in just a few days, during Wasm I/O, after which we will undraft this PR and update it to the latest tag.

Let me know if you'd rather merge this PR before the official release. This draft PR is intended to let your CI checks run and verify everything is in order before our final release.

Since you are using wasilibs, you might also want to wait for them to update upstream instead.

This will update [wazero](https://wazero.io/) to v1.7.0.
The v1.7.0 release marks a milestone in the wazero project, replacing
our old compiler architecture with a [new optimizing compiler backend.][docs].
It also introduces experimental support to the thread spec.

We will officially announce the final v1.7.0 release in just a few days,
during [Wasm I/O](https://wasmio.tech/), after which we will undraft
this PR and update it to the latest tag.

Let me know if you'd rather merge this PR before the official
release. This draft PR is intended to let your CI checks run and verify
everything is in order before our final release.

Since you are using wasilibs, you might also want to wait for them
to update upstream instead.

[docs]: https://wazero.io/docs/how_the_optimizing_compiler_works/

Signed-off-by: Edoardo Vacchi <[email protected]>
@kyleconroy
Copy link
Collaborator

This draft PR is intended to let your CI checks run and verify everything is in order before our final release.

Sounds good. I'd like to wait for the official tag before merging. I appreciate the draft PR though

Since you are using wasilibs, you might also want to wait for them to update upstream instead.

Yeah, I think that's probably the safest thing to do.

Signed-off-by: Edoardo Vacchi <[email protected]>
@evacchi
Copy link
Author

evacchi commented Mar 16, 2024

meanwhile I have updated this PR v1.7.0 final!

@evacchi evacchi marked this pull request as ready for review March 16, 2024 06:33
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.

2 participants