chore(release): archied v1.25.0 archie v1.25.0
This commit is contained in:
1 parent
812ad71ac7
commit
f78272fb17
2 files changed
+18
No files matched your search
@@ -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
|
||||
|
||||
@@ -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,
|
||||
|
||||
Reference in new issue
Block a user