Upgrade and rollback
- Existing browser sessions require one fresh login after upgrading. Keep each instance's settings path stable and preserve its private signing-state file across restarts. See session security and migration.
- Ranger automatically upgrades its task database from schema 1 or 2 to schema 3. Older builds cannot open the upgraded database. If rollback may be needed, stop the bridge and back up the entire private Ranger data directory before upgrading; restore that pre-upgrade backup when rolling back. See Ranger deployment and rollback guidance.
What's Changed
Breaking Changes
- Add workspace and agent mentions to Ranger by @powerfooI in #375
- Separate session signing keys and add optional PIN login by @powerfooI in #382
Features
- Offer Open worktree for workspaces Herdr did not open as worktrees by @thiblahute in #377
- Surface specific Ranger task creation errors by @Epsirom in #379
Fixes
- Fix Ranger custom thinking effort and workspace permissions by @powerfooI in #374
- Prevent duplicate terminal composition finalization by @powerfooI in #378
Documentation
- Refresh 0.8.0 product screenshots and showcase Ranger by @powerfooI in #381
Full Changelog: v0.8.0...v0.8.1