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

use released WASI Preview 2 (version 0.2.0) wits #7817

Merged
merged 3 commits into from
Jan 25, 2024

Conversation

pchickey
Copy link
Contributor

Pending the WASI Preview 2 launch vote at the 1/25 WASI Subgroup meeting, this updates all of the WASI wit files, as well as all use sites, to expect and use version 0.2.0.

There are no functional changes between the latest release candidates used in tree, and version 0.2.0, aside from changing the version of each wit package.

@github-actions github-actions bot added the wasi Issues pertaining to WASI label Jan 25, 2024
@pchickey
Copy link
Contributor Author

pchickey commented Jan 25, 2024

Preview 2 vote passed so this is ready to go.

@pchickey pchickey marked this pull request as ready for review January 25, 2024 17:43
@pchickey pchickey requested a review from a team as a code owner January 25, 2024 17:43
@pchickey pchickey requested review from alexcrichton and removed request for a team January 25, 2024 17:43
Copy link
Member

@alexcrichton alexcrichton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@alexcrichton alexcrichton added this pull request to the merge queue Jan 25, 2024
alexcrichton pushed a commit that referenced this pull request Jan 25, 2024
* WASI: copy in the version 0.2.0 wits

* wasmtime's wits: use versions 0.2.0 of wasi packages

* bindgens and other fixed version strings: change 0.2.0-rc-etc to 0.2.0
Merged via the queue into main with commit 1c335c1 Jan 25, 2024
20 checks passed
@alexcrichton alexcrichton deleted the pch/release_preview2 branch January 25, 2024 18:24
alexcrichton added a commit that referenced this pull request Jan 25, 2024
* Release Wasmtime 17.0.0

[automatically-tag-and-release-this-commit]

* Change update of gcc on MinGW (#7760)

Try not passing `-y -u` to `pacman` to avoid full system updates.
Currently full system updates might update the `msys2-runtime` package
before actually updating the package we requested, meaning that this
might not actually update anything given an update. This is what's
currently happening on CI which is breaking due to an update of gcc not
actually updating gcc. I'm mostly reading the invocation in
rust-lang/rust CI and seeing that it doesn't pass `-y -u` and hopeing
that by copying that here things might work.

prtest:full

* use released WASI Preview 2 (version 0.2.0) wits (#7817)

* WASI: copy in the version 0.2.0 wits

* wasmtime's wits: use versions 0.2.0 of wasi packages

* bindgens and other fixed version strings: change 0.2.0-rc-etc to 0.2.0

* Enable the component model by default

This commit enables the component model by default in the embedding API
and the CLI. This means that an opt-in of `-W component-model` is no
longer required and additionally `.wasm_component_model(true)` is no
longer required. Note that this won't impact existing embeddings since
the component model feature doesn't do much less `wasmtime::component`
is used, and if that's being used this is probably good news for you.

* Add release notes for 17.0.0

* Fix non-component-model build

---------

Co-authored-by: Wasmtime Publish <wasmtime-publish@users.noreply.github.com>
Co-authored-by: Alex Crichton <alex@alexcrichton.com>
Co-authored-by: Pat Hickey <phickey@fastly.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wasi Issues pertaining to WASI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants