|
| 1 | +--- |
| 2 | +title: "Wasmtime LTS Releases" |
| 3 | +author: "Alex Crichton" |
| 4 | +date: "2025-04-22" |
| 5 | +github_name: "alexcrichton" |
| 6 | +excerpt_separator: <!--end_excerpt--> |
| 7 | +--- |
| 8 | + |
| 9 | +[Wasmtime](https://wasmtime.dev/) is a lightweight WebAssembly runtime built for |
| 10 | +speed, security, and standards-compliance. Wasmtime now supports |
| 11 | +long-term-support (LTS) releases that are maintained with security fixes for 2 |
| 12 | +years after their initial release. |
| 13 | + |
| 14 | +<!--end_excerpt--> |
| 15 | + |
| 16 | +The Wasmtime project releases a new version once a month with new features, bug |
| 17 | +fixes, and performance improvements. Previously though these releases were only |
| 18 | +supported for 2 months meaning that embedders needed to follow the Wasmtime |
| 19 | +project pretty closely to receive security updates. This rate of change can be |
| 20 | +too fast for users so Wasmtime now supports [LTS |
| 21 | +releases](https://github.com/bytecodealliance/rfcs/blob/main/accepted/wasmtime-lts.md). |
| 22 | + |
| 23 | +Every 12th version of Wasmtime will now be considered an LTS release and will |
| 24 | +receive security fixes for 2 years, or 24 months. This means that users can now |
| 25 | +update Wasmtime once-a-year instead of once-a-month and be guaranteed that they |
| 26 | +will always receive security updates. Wasmtime's 24.0.0 release has been |
| 27 | +retroactively classified as a LTS release and will be supported until August 20, |
| 28 | +2026. Wasmtime's upcoming 36.0.0 release on August 20, 2025 will be supported |
| 29 | +until August 20, 2027, meaning that users will have one year starting in August |
| 30 | +to upgrade from 24.0.0 to 36.0.0. |
| 31 | + |
| 32 | +You can view a table of Wasmtime's releases [in the documentation |
| 33 | +book](https://docs.wasmtime.dev/stability-release.html) which has information on |
| 34 | +all currently supported releases, upcoming releases, and information about |
| 35 | +previously supported releases. The high-level summary of Wasmtime's LTS release |
| 36 | +channel is: |
| 37 | + |
| 38 | +* LTS releases receive patch updates for 2 years after their initial release. |
| 39 | +* Patch releases are guaranteed to preserve API compatibility. |
| 40 | +* Patch releases strive to maintain tooling compatibility (e.g. the Rust version |
| 41 | + required to compile Wasmtime) from the time of release. Depending on EOL dates |
| 42 | + from components such as GitHub Actions images, however, this may need minor |
| 43 | + updates. |
| 44 | +* Patch releases are guaranteed to be issued for any security bug found in |
| 45 | + historical releases of Wasmtime. |
| 46 | +* Patch releases may be issued to fix non-security released bugs as they are |
| 47 | + discovered. The Wasmtime project will rely on contributions to provide |
| 48 | + backports for these fixes. |
| 49 | +* Patch releases will not be issued for new features to Wasmtime, even if a |
| 50 | + contribution is made to backport a new feature. |
| 51 | + |
| 52 | +If you're a current user of Wasmtime and would like to use an LTS release then |
| 53 | +it's recommended to either downgrade to the 24.0.0 version or wait for this |
| 54 | +August to upgrade to the 36.0.0 version. Wasmtime 34.0.0, to be released June |
| 55 | +20, 2025, will be supported up until the release of Wasmtime 36.0.0 on August |
| 56 | +20, 2025. |
0 commit comments