Repository navigation
v0.7.2
More reliable container upgrades
This patch release makes container upgrades more reliable when package names change between images. Previously, two unavailable package names could block restoration of dozens of valid packages; upgrades now restore what is available and identify what still needs attention. Recovery inspection and upgrade previews also work more predictably with stopped containers.
Highlights
- Restore available Ubuntu/Debian packages even when some old package names or requested versions are unavailable.
- Inspect and resume saved recovery plans in stopped containers, including containers using the managed MCP bridge, while preserving their original running state.
- Preview upgrades of stopped containers without starting containers or exporting their filesystems. The preview clearly identifies installed-state details that were not inspected.
- Distinguish failed recovery actions from deferred ones and identify incomplete recovery in upgrade completion messages. Standalone recovery now returns a nonzero exit status when a selected action fails; successful container recreation still returns zero.
- Find common setup and everyday commands more easily in the reorganized README.
Updating to v0.7.2
- Repository: pull the updated host checkout to use the fixes.
agentctl refresh: not required for the v0.7.2 fixes. If you skipped v0.7.1, refresh existing containers that should receive its Codex launch fix, as described in the v0.7.1 release notes.agentctl upgrade: not required to apply these host-side fixes.- Recreate containers: not required.
- Rebuild images: not required.
Existing recovery plans can be resumed with agentctl upgrade restore --interactive. Unavailable package entries still require review; replacements are not guessed and failed entries are not automatically dismissed.