Changelog
Reinstate Changelog and Release Notes
The latest published Reinstate tag is v0.1.0-rc.8, dated July 29, 2026. RC8 tightens cross-device project mapping and restore verification, improves additional-device storage validation, and keeps the public installers and acceptance evidence pinned to one release candidate.
- Last verified
- Current release
- v0.1.0-rc.8
- Release status
- pre-1.0 release candidate
- Owner
- Harjot Singh Rana
Unreleased
Current unreleased website work adds the SEO, answer-engine, AI-search, and social-preview foundation and introduces signed website-vYYYY.MM.DD.N deployment tags. A website tag can publish reviewed site changes from current main while the public CLI and installer routes remain pinned to the separately signed v0.1.0-rc.8 release. It is not a new Reinstate version or evidence that the remaining RC8 acceptance gates have closed.
The repository'scanonical CHANGELOG.md is authoritative if this summary and the current branch differ.
v0.1.0-rc.8 · July 29, 2026
Cross-device path and restore correctness
- Codex rollout working directories now resolve to configured canonical project IDs, exclude unmapped projects, normalize source roots on export, and reject duplicate mappings.
- The Claude Code adapter uses canonical project mapping to compute destination-specific project directories and verifies the restored session at the exact planned vendor path.
- Pull dry-runs report
would pullinstead of implying that sessions were already restored.
Setup and storage validation
- An additional device validates the encrypted remote manifest with a readable object request, avoiding Cloudflare R2's generic failure for a metadata-only probe.
- Setup preserves and confirms an existing absolute
REINSTATE_HOMEinstead of silently falling back to the default home. - The missing-config error remains redacted rather than exposing an absolute local config path.
Release and roadmap clarity
- Public installers, setup prompts, and compatibility evidence are pinned to RC8.
- Production deployment requires the signed-tag release workflow and verifies immutable and promoted installer routes byte for byte.
- Post-Phase-1 direction now documents universal non-secret agent configuration without expanding current CLI claims.
View the v0.1.0-rc.8 tag on GitHub.
Release-candidate history
| Release | Date | Primary focus |
|---|---|---|
| v0.1.0-rc.8 | Session liveness detection that no longer depends on an open file handle. | |
| v0.1.0-rc.7 | Session-scoped restore safety that no longer blocks on unrelated running agents. | |
| v0.1.0-rc.6 | Canonical project mapping, exact restore checks, and remote-manifest validation. | |
| v0.1.0-rc.5 | Safer re-initialization, joined-profile checks, and bounded installer confirmation. | |
| v0.1.0-rc.4 | Destination-aware Claude paths and portable Codex structural paths. | |
| v0.1.0-rc.3 | Tested version ranges, fail-closed setup checks, and a dependency security patch. | |
| v0.1.0-rc.2 | Signed-tag verification correction. | |
| v0.1.0-rc.1 | Initial Phase 0 and Phase 1 release-candidate foundation. |
What the first release candidate established
RC1 introduced the Cobra CLI, versioned local state, device detection, diagnostics, verified installers, S3-compatible storage, age encryption, path mapping, manifests, push and pull, conflicts, Claude Code and Codex adapters, native keyring credentials, restore backups, and the synthetic compatibility-test foundation. It also established rein as the short alias for the reinstate binary.
How to read pre-1.0 release notes
A release candidate is published for testing before stable v0.1 certification. Read every intermediate release note before replacing a binary because compatibility behavior, session artifact formats, setup validation, and release gates may still change.
- Pin an explicit release in automated setup.
- Verify checksums before installing.
- Run
rein setup checkafter agent or Reinstate upgrades. - Use pull dry-runs and maintain independent backups of important work.