0.9.198
2026-09-11Sma1lboy
Every published release of Rove, newest first. Each entry is a version tag, and each line under it is one change that shipped with that tag.
or pin one
Takes the newest build on your channel. A bare version pins one, and a channel name switches lines.
Fetched live from the repository's releases. Entries are never edited after the fact: a mistake in a shipped release is corrected by the next one. A tag can carry several changes, each from its own pull request. Where a release separates patch changes from minor ones, the two are listed under separate headings.
Loading Fetching the full list from api.github.com
| Stage | Result | When |
|---|---|---|
| Changeset | .changeset/*.md | Written with the PR |
| Bump | 0.9.190 → .191 | Consumed on merge |
| Tag | v0.9.198 | Pushed to main |
| Publish | @sma1lboy/rove | Installable once the test gates pass |
| Update | rove update | On your machine |
Every build passes the same test gates between the tag and the publish.
Each change brings its own release note. The pull request adds a Markdown file under .changeset/. Merging consumes those files, writes the new version and appends their text to CHANGELOG.md.
The tag is pushed from main, the publish happens in CI, and the GitHub release body is that changelog entry verbatim, so this list is fetched, not written.
| latest | The stable line: batched, reviewed releases. This is what a plain install gives you, and what the list above shows. |
|---|---|
| nightly | An automated daily cut from main. Same test gates, but its contents have not been reviewed as a set. |
You do not configure a channel. The build you are running is the channel. Update checks follow whichever one you installed from, and rove update with no arguments never moves you between them.
rove update list browses recent versions and rove update dry-run prints the command without running it. Updates go through whichever package manager owns the rove on your PATH, so a new version cannot land in a shadowed prefix.