Release Wasmtime 0.34.1 #3812
Merged
Release Wasmtime 0.34.1 #3812
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[automatically-tag-and-release-this-commit]
github-actions
bot
force-pushed
the
ci/bump-version
branch
from
9a1fb8b to
dbbb182
Compare
alexcrichton
approved these changes
Feb 16, 2022
github-actions
bot
added
cranelift
Subscribe to Label Action
This issue or pull request has been labeled: "cranelift", "cranelift:meta", "cranelift:module", "cranelift:wasm", "isle", "wasmtime:docs"
Thus the following users have been cc'd because of the following labels:
To subscribe or unsubscribe from this label, edit the |
|
Hi, seems some artifacts are missing from the release, like the binary for |
alexcrichton
added a commit
to alexcrichton/wasmtime
that referenced
this pull request
Feb 22, 2022
Looks like the 0.34.1 release is missing artifacts and some jobs building artifacts ended up being cancelled because of API rate limits being hit on the builders. Artifacts are uploaded to the job, however, which means we can always go back and grab them to upload them, unless the whole job was cancelled. For 0.34.1 it looks like the Linux builder hit an error but its error then subsequently cancelled the Windows builders, so we don't actually have artifacts for Windows for the 0.34.1 release. This will hopefully prevent this from causing further issues in the future where if one builder hits an error while uploading artifacts the others will continue and we can manually upload what's missing if necessary. cc bytecodealliance#3812
|
Oops thanks for pointing that out @TerrorJack! The CI build for 0.34.1 had artifacts for Linux I manually uploaded to the release, but unfortunately we also don't have Windows artifacts due to the job being cancelled which hopefully #3832 will address in the future. If that's an issue though we can delete the release and re-run the build to get artifacts again. |
alexcrichton
added a commit
that referenced
this pull request
Feb 22, 2022
Looks like the 0.34.1 release is missing artifacts and some jobs building artifacts ended up being cancelled because of API rate limits being hit on the builders. Artifacts are uploaded to the job, however, which means we can always go back and grab them to upload them, unless the whole job was cancelled. For 0.34.1 it looks like the Linux builder hit an error but its error then subsequently cancelled the Windows builders, so we don't actually have artifacts for Windows for the 0.34.1 release. This will hopefully prevent this from causing further issues in the future where if one builder hits an error while uploading artifacts the others will continue and we can manually upload what's missing if necessary. cc #3812
mpardesh
pushed a commit
to avanhatt/wasmtime
that referenced
this pull request
Mar 17, 2022
Looks like the 0.34.1 release is missing artifacts and some jobs building artifacts ended up being cancelled because of API rate limits being hit on the builders. Artifacts are uploaded to the job, however, which means we can always go back and grab them to upload them, unless the whole job was cancelled. For 0.34.1 it looks like the Linux builder hit an error but its error then subsequently cancelled the Windows builders, so we don't actually have artifacts for Windows for the 0.34.1 release. This will hopefully prevent this from causing further issues in the future where if one builder hits an error while uploading artifacts the others will continue and we can manually upload what's missing if necessary. cc bytecodealliance#3812
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automated pull request from CI which is intended to
notify maintainers that it's time to release Wasmtime version
0.34.1. Version numbers have been bumped
in this PR automatically and the release process will automatically
enter the next stages once this PR is merged.
It's recommended that maintainers double-check that RELEASES.md
is up-to-date. If not please feel free to push to this PR any
modifications to the release notes. Additionally before merging it's
probably best to double-check the release process and make sure that
everything is ship-shape.