-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Release Wasmtime 2.0.0 #5081
Release Wasmtime 2.0.0 #5081
Conversation
[automatically-tag-and-release-this-commit]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll give this a few hours for folks to wake up and raise objections if there are any, otherwise I'll merge later this afternoon.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just checked the release-2.0.0 branch with cg_clif again. No regressions.
"Push tagged release" has finished, but "Publish on crates.io" hasn't even started yet. Did something go wrong? |
Thanks for the heads up, looks like CI issues. I pushed the tag manually and will fix the CI issues. |
Publishing cranelift-jit failed:
and so did a couple of other crates like wasmtime-wasi-crypt:
|
Indeed, it actually kept going and it's expected to fail a lot. It failed to publish everything but |
This is an automated pull request from CI which is
intended to notify maintainers that it's time to release Wasmtime
2.0.0. The release branch was created roughly two weeks ago
and it's now time for it to be published and released.
It's recommended that maintainers double-check that RELEASES.md
is up-to-date and that there are no known issues before merging this
PR. When this PR is merged a release tag will automatically be
created, crates will be published, and CI artifacts will be produced.