Wasmtime GitHub notifications bot (Mar 22 2022 at 19:07): Wasmtime GitHub notifications bot (Mar 22 2022 at 19:07):alexcrichton commented on issue #3955:
Some examples of PRs:
- PR on the 5th of the month to update the major version number
- PR on the 20th to
mainto update the release date- PR on the 20th to
release-x.y.zto make the release- PR for a patch release, made to
release-x.y.zNote that I've included a major version bump to 0.36.0 in this PR since that's the next version of Wasmtime, and that'll be necessary to bootstrap this process. That's because
mainwill always be a version ahead of the latest release branch.
Wasmtime GitHub notifications bot (Mar 22 2022 at 19:15):github-actions[bot] commented on issue #3955:
Subscribe to Label Action
cc @cfallin, @fitzgen
<details>
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:
- cfallin: isle
- fitzgen: isle
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
Wasmtime GitHub notifications bot (Apr 01 2022 at 15:01):alexcrichton commented on issue #3955:
I added some more notes here on performing a security release, specifically indicating that we should open a version-bump PR ahead-of-time as we announce the intent to make patch releases. This gives us some extra runway to fix any issues with CI that arise, for example the backports included in https://github.com/bytecodealliance/wasmtime/pull/3984.
Last updated: Nov 22 2024 at 16:03 UTC