Skip to content

Release Wasmtime 0.32.0#3499

Closed
wasmtime-publish wants to merge 1 commit into
mainfrom
ci/bump-version
Closed

Release Wasmtime 0.32.0#3499
wasmtime-publish wants to merge 1 commit into
mainfrom
ci/bump-version

Conversation

@wasmtime-publish

Copy link
Copy Markdown
Collaborator

This is an automated pull request from CI which is intended to
notify maintainers that it's time to release Wasmtime version
0.32.0. 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.

[automatically-tag-and-release-this-commit]
@github-actions github-actions Bot added cranelift Issues related to the Cranelift code generator cranelift:area:peepmatic cranelift:meta Everything related to the meta-language. cranelift:module cranelift:wasm labels Nov 1, 2021
@github-actions

github-actions Bot commented Nov 1, 2021

Copy link
Copy Markdown

Subscribe to Label Action

cc @fitzgen

Details This issue or pull request has been labeled: "cranelift", "cranelift:area:peepmatic", "cranelift:meta", "cranelift:module", "cranelift:wasm"

Thus the following users have been cc'd because of the following labels:

  • fitzgen: cranelift:area:peepmatic

To subscribe or unsubscribe from this label, edit the .github/subscribe-to-label.json configuration file.

Learn more.

@alexcrichton

Copy link
Copy Markdown
Member

I don't know why this workflow was scheduled, but it shouldn't have been...

@alexcrichton alexcrichton deleted the ci/bump-version branch November 1, 2021 14:05
alexcrichton added a commit to alexcrichton/wasmtime that referenced this pull request Nov 8, 2021
Either I don't understand cron or GitHub doesn't understand cron. It's
not clear which. I think that
bytecodealliance#3511 may have fallen
within our schedule but it was supposed to be on a weekday. Otherwise
bytecodealliance#3499 was certainly
spurious. This commit moves to a simpler "just do it on the same day
each month" and we can manually figure out weekdays and such. Hopefully
this should reduce the number of spurious PRs we're getting to bump
versions.

This also removes the script to force a version bump since I found a
button on the GitHub UI to do the same thing. Additionally I've updated
the patch-release documentation to use this button.
alexcrichton added a commit to alexcrichton/wasmtime that referenced this pull request Nov 8, 2021
Either I don't understand cron or GitHub doesn't understand cron. It's
not clear which. I think that
bytecodealliance#3511 may have fallen
within our schedule but it was supposed to be on a weekday. Otherwise
bytecodealliance#3499 was certainly
spurious. This commit moves to a simpler "just do it on the same day
each month" and we can manually figure out weekdays and such. Hopefully
this should reduce the number of spurious PRs we're getting to bump
versions.

This also removes the script to force a version bump since I found a
button on the GitHub UI to do the same thing. Additionally I've updated
the patch-release documentation to use this button. Note that this
button takes inputs as well which means we can further automate patch
releases to look even more like normal release process, differing only
in one part of the argument used to trigger the workflow.
alexcrichton added a commit that referenced this pull request Nov 8, 2021
* Change the bump-version workflow's schedule

Either I don't understand cron or GitHub doesn't understand cron. It's
not clear which. I think that
#3511 may have fallen
within our schedule but it was supposed to be on a weekday. Otherwise
#3499 was certainly
spurious. This commit moves to a simpler "just do it on the same day
each month" and we can manually figure out weekdays and such. Hopefully
this should reduce the number of spurious PRs we're getting to bump
versions.

This also removes the script to force a version bump since I found a
button on the GitHub UI to do the same thing. Additionally I've updated
the patch-release documentation to use this button. Note that this
button takes inputs as well which means we can further automate patch
releases to look even more like normal release process, differing only
in one part of the argument used to trigger the workflow.

* Fix a typo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cranelift:meta Everything related to the meta-language. cranelift:module cranelift:wasm cranelift Issues related to the Cranelift code generator

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants