Changes in stability-release.md

c190d7c4 - Document the effect of CI outages on releases (#12521)

Wed, 04 Feb 2026 21:25:20 +0000

Document the effect of CI outages on releases (#12521)* Document the effect of CI outages on releasesClearly specify in our documentation that we are entirely subject to theshims of Azure and GitHub Actions. If they're down we just simply can'tdo a release and there's nothing we can do about it. Document this bothfor ourselves and for external users to understand our own limitations.An offer is made as well in case a company is willing to donateresources (e.g. money or engineering) to improve the situation as well.* Update docs/stability-release.mdCo-authored-by: Nick Fitzgerald ---------Co-authored-by: Nick Fitzgerald List of files: /wasmtime-44.0.1/docs/stability-release.md

2de55ccf - Add documentation for Wasmtime's LTS releases (#10481)

Mon, 31 Mar 2025 18:49:16 +0000

Add documentation for Wasmtime's LTS releases (#10481)* Add documentation for Wasmtime's LTS releasesWith Wasmtime's [LTSreleases](https://github.com/bytecodealliance/rfcs/pull/42) this commitdocuments the various process changes and updates to our releaseprocess. Additionally some improvements are made to the releasedocumentation with respect to showing current versions.* Refactor some backport criteria docs* Review comments List of files: /wasmtime-44.0.1/docs/stability-release.md

24a2f8ca - Document wasmtime-rb (#5485)

Thu, 22 Dec 2022 01:02:31 +0000

Document wasmtime-rb (#5485)* Document wasmtime-rb * Fix typo in `docs/lang-ruby.md`, improve copy List of files: /wasmtime-44.0.1/docs/stability-release.md

5f53fd5c - Clarify patch release criteria (#3940)

Fri, 18 Mar 2022 14:09:50 +0000

Clarify patch release criteria (#3940)In today's Wasmtime meeting we discussed the acceptance criteria for patch releases for Wasmtime and Cranelift. The criteria we came up with were: * Cranelift will get a patch release for any miscompilation, whether or not it affects Wasmtime. * Wasmtime will get a patch release for security issues and bugs which seriously hinder usability. The consensus at the time was that due to Wasmtime's monthly release schedule we want to be pretty strict about what generates a patch release, hence the threshold being at serious bugs as opposed to any bugs found. This commit attempts to update the `stability-release.md` document with our documented release process. The release cadence section is brought up to date, the Wasmtime section was edited slightly (it largely already said this which I only just realized), and a Cranelift section was added. List of files: /wasmtime-44.0.1/docs/stability-release.md

807b528b - Automate more of Wasmtime's release process (#3422)

Tue, 26 Oct 2021 15:25:40 +0000

Automate more of Wasmtime's release process (#3422)* Automate more of Wasmtime's release process This change revamps the release process for Wasmtime and intends to make it nearly 100% automated for major release and hopefully still pretty simple for patch releases. New workflows are introduced as part of this commit: * Once a month a PR is created with major version bumps * Specifically hinted commit messages to the `main` branch will get tagged and pushed to the main repository. * On tags we'll now not only build releases after running CI but additionally crates will be published to crates.io. In conjunction with other changes this means that the release process for a new major version of Wasmtime is simply merging a PR. Patch releases will involve running some steps locally but most of the nitty-gritty should be simply merging the PR that's generated. * Use an anchor in a regex List of files: /wasmtime-44.0.1/docs/stability-release.md

bf526b62 - Add book documentation skeleton and auto-publish from CI (#435)

Tue, 29 Oct 2019 14:55:51 +0000

Add book documentation skeleton and auto-publish from CI (#435)This commit adds the skeleton of a new set of documentation for `wasmtime` in the existing `docs` directory. This documentation is organized and compiled with [mdbook] which the Rust project uses for most of its own documentation as well. At a previous meeting we brainstormed a rough skeleton of what the documentation in this book would look like, and I've transcribed that here for an example of how this is rendered and how it can be laid out. No actual documentation is written yet. This commit also additionally adds necessary support to auto-publish both this book documentation and API documentation every time a commit is pushed to the `master` branch. All HTML will be automatically pushed to the `gh-pages` branch so long as the CI passes, and this should get deployed to https://cranestation.github.io/wasmtime. I've done a few dry-runs and I think this'll all work, but we'll likely tweak a few things here and there after running this through CI to make sure everything looks just as we'd like. My hope though is that after this lands we can start actually filling out all the documentation and being able to review it as well. [mdbook]: https://crates.io/crates/mdbook List of files: /wasmtime-44.0.1/docs/stability-release.md