1# Release Process
2
3This is intended to serve as documentation for Wasmtime's release process. It's
4largely an internal checklist for those of us performing a Wasmtime release, but
5others might be curious in this as well!
6
7To kick off the release process someone decides to do a release. Currently
8there's not a schedule for releases or something similar. Once the decision is
9made (there's also not really a body governing these decisions, it's more
10whimsical currently, or on request from others) then the following steps need to
11be executed to make the release:
12
131. `git pull` - make sure you've got the latest changes
141. Update the version numbers in `Cargo.toml` for all crates
15  * Edit `scripts/bump-wasmtime-version.sh`, notable the `version` variable
16  * Run the script
17  * Commit the changes
181. Make sure `RELEASES.md` is up-to-date, and fill it out if it doesn't have an
19   entry yet for the current release.
201. Send this version update as a PR to the `wasmtime` repository, wait for a merge
211. After merging, tag the merge as `vA.B.C`
221. Push the tag to the repository
23  * This will trigger the release CI which will create all release artifacts and
24    publish them to GitHub releases.
251. Run `scripts/publish-all.sh` to publish all crates to crates.io
26
27And that's it, then you've done a Wasmtime release.
28