Rove

Changelog

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.

Releases

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

0.9.198

2026-09-11Sma1lboy

  • #989
    Rove now drives pi and omp as first-class engines, with the same activity badges as the other built-ins.
  • #990
    Find out what Rove is forking.

0.9.190

2026-09-11Sma1lboy

  • #988
    Typing in a Rove terminal no longer lags a frame behind the same shell outside Rove.

0.9.189

2026-09-11Sma1lboy

  • #987
    A tab running a custom engine no longer reads as a bare shell.

How a change becomes a release

Stage Result When
Changeset.changeset/*.mdWritten with the PR
Bump0.9.190 → .191Consumed on merge
Tagv0.9.198Pushed to main
Publish@sma1lboy/roveInstallable once the test gates pass
Updaterove updateOn 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.

Two channels

latestThe stable line: batched, reviewed releases. This is what a plain install gives you, and what the list above shows.
nightlyAn 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.