From f78272fb17657b34b3cb7d8323fd8511ca282f38 Mon Sep 17 00:00:00 2001 From: Sam Catlow Date: Tue, 15 Sep 2026 00:22:15 +1000 Subject: [PATCH] chore(release): archied v1.25.0 archie v1.25.0 --- CHANGELOG.archie.md | 5 +++++ CHANGELOG.archied.md | 13 +++++++++++++ 2 files changed, 18 insertions(+) diff --git a/CHANGELOG.archie.md b/CHANGELOG.archie.md index f1798e882..de4fd0282 100644 --- a/CHANGELOG.archie.md +++ b/CHANGELOG.archie.md @@ -1,5 +1,10 @@ # archie-agent changelog +## [1.25.0] - 2026-09-15 + +- chore: no user-facing changes; versioned so the 1.25.0 release tags both + components at the same commit + ## [1.23.0] - 2026-09-12 The agent runtime now reaches task state through the State Store gRPC contract diff --git a/CHANGELOG.archied.md b/CHANGELOG.archied.md index 93cd28898..1b822314f 100644 --- a/CHANGELOG.archied.md +++ b/CHANGELOG.archied.md @@ -1,5 +1,18 @@ # archied changelog +## [1.25.0] - 2026-09-15 + +- 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. + ## [1.24.0] - 2026-09-12 Makes 1.23.0 deployable. That release split archied into separate processes,