Release 1.25.0
News ·
archied
- fix(update): resolve releases without a checkout, and fail loudly when it cannot
- fix(update): back up the task store the daemon actually uses, or refuse
- fix(update): build each component from its own approved release tag
Components are independently versioned, so the newest archied/v* and
archie/v* tags usually sit on different commits. The installer required both
tags to resolve to one commit whenever both components changed, which refused
every update once the two newest releases diverged – a deployment stuck on
1.22.0 could not take any update. Each component now builds from its own
approved tag.
archie-agent
- chore: no user-facing changes; versioned so the 1.25.0 release tags both components at the same commit