DocsThe ecosystem
Releases
Rahti is in alpha. Alpha runs in two-month cycles, each one taking patch releases as they are ready and ending in an upgrade the next cycle builds on, until beta opens in February 2027. This page is the schedule, where the framework is on it, and every version published so far.
Release schedule
Alpha is split into two-month cycles. Inside a cycle, patch releases ship whenever there is something to ship — a fix, a convention change, a new page of the framework. When a cycle closes, its last release is the upgrade the next cycle starts from. Three alpha cycles end the alpha line in January 2027; beta begins in February.
Release phases
| Phase | When | What it means for your project |
|---|---|---|
| Alpha | Aug 2026 – Jan 2027 | The API is still being settled. Any release may change a public signature, a convention or a generated file, and the change is written up in the convention documents that cargo rahti upgrade refreshes. |
| Beta | From Feb 2027 | The alpha line has ended. The surface alpha settled is kept; releases are fixes and hardening rather than new API. |
| Stable | After beta | Not scheduled yet. A date is set once beta has been in use long enough to earn one. |
Release cycles
Status follows the calendar: a cycle is Current between its first and last day, Ended after it, and Planned before it opens.
| Cycle | Window | First release | Latest release | Releases | Status |
|---|---|---|---|---|---|
| Alpha 1 | Aug 2026 – Sep 2026 | 0.0.12026-08-12 | 0.0.392026-09-30 | 39 | Ended |
| Alpha 2 | Oct 2026 – Nov 2026 | 0.0.402026-10-01 | 0.0.422026-10-01 | 3 | Current |
| Alpha 3 | Dec 2026 – Jan 2027 | — | — | 0 | Planned |
| Beta | From Feb 2027 | — | — | 0 | Planned |
| Cycle | Focus |
|---|---|
| Alpha 1 | First publication. Routing, rendering, PulsePoint, RPC, auth and the production middleware stack. |
| Alpha 2 | Patches and upgrades on top of Alpha 1, driven by what applications built on it run into. |
| Alpha 3 | The last alpha cycle. Closes out the API changes alpha is for, so beta starts from a settled surface. |
| Beta | The alpha line ends here. Fixes and hardening rather than new surface. |
Every release
Read live from crates.io, so a release appears here the day it is published. A cycle's releases are the ones published inside its window.
Alpha 1 — 39 releases
- v0.0.392026-09-30
- v0.0.382026-09-23
- v0.0.372026-09-15
- v0.0.362026-09-15
- v0.0.352026-09-15
- v0.0.342026-09-13
- v0.0.332026-09-10
- v0.0.322026-09-07
- v0.0.312026-09-07
- v0.0.302026-09-02
- v0.0.292026-09-01
- v0.0.282026-09-01
- v0.0.272026-08-31
- v0.0.262026-08-30
- v0.0.252026-08-28
- v0.0.242026-08-23
- v0.0.232026-08-22
- v0.0.222026-08-22
- v0.0.212026-08-22
- v0.0.202026-08-21
- v0.0.192026-08-20
- v0.0.182026-08-17
- v0.0.172026-08-14
- v0.0.162026-08-14
- v0.0.152026-08-14
- v0.0.142026-08-14
- v0.0.132026-08-14
- v0.0.122026-08-14
- v0.0.112026-08-14
- v0.0.102026-08-14
- v0.0.92026-08-14
- v0.0.82026-08-13
- v0.0.72026-08-13
- v0.0.62026-08-13
- v0.0.52026-08-13
- v0.0.42026-08-13
- v0.0.32026-08-13
- v0.0.22026-08-13
- v0.0.12026-08-12
Upgrading during alpha
Every alpha version is 0.0.x. Cargo treats each 0.0.x as incompatible with every other, so cargo update never moves a project from one alpha release to the next — the move is always deliberate. Upgrade the CLI, then let it move the project:
cargo install cargo-rahti
cargo rahti upgradeThat refreshes the scaffold files you have not edited and moves the rahti and rahti-build pins together. Official packages explains what it moves and what it deliberately leaves alone.
The other release lines
This schedule is the framework line's: rahti, rahti-macros, rahti-build, cargo-rahti and rahti-mcp, released in lockstep. The UI, icon and native packages have version lines of their own and release when they need to — see Official packages. Everything is published from one crates.io account.