diff --git a/CHANGELOG.md b/CHANGELOG.md index a9e53562c..cff8b72f2 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,6 +5,39 @@ release's per-component sections are labelled beneath its heading. ## [Unreleased] +## [1.44.1] - 2026-09-29 + +### archied + +Two fixes to tasks that could not get past their workflow definition. + +- **Approving a task no longer parks it again.** A task requeued under a + different workflow kept the previous run's definition pinned, so the worker + refused to compile the dispatch — it named `feasibility` while the row named + `implement` — and the task parked immediately, identically on every further + approval, which left `decline` as the only working operator action. + The daemon now re-pins whenever the pinned definition's id disagrees with the + task's workflow. A pin that is present, digest-valid and id-consistent is + still a strict no-op, so an operator's own definition override survives a + dispatch unchanged. +- **A shipped workflow definition now reaches an existing install.** A stored + seed was consulted only for a resource the store did not already hold, so a + document that changed in the build never reached a database an earlier + release had seeded. For workflow definitions that is a total outage rather + than a stale setting: the collection validates as one document, so a stored + step type this build no longer has failed every task's pin, whatever workflow + the task named — and the documented recovery, removing the resource and + restarting, wrote nothing either, because the store answered the seed's known + request ID from a history that outlives the resource. A seed now refreshes a + kind it wrote the newest revision of and re-creates a resource that is gone, + while an operator's own replacement is never undone. + +### archie-agent + +The runtime image is rebuilt with this release and links the shared workflow +package carrying the definition-id helper above. Hosts that run agent +containers need `docker compose pull agent` after updating to pick it up. + ## [1.44.0] - 2026-09-29 ### archied diff --git a/docs/news/redirects.json b/docs/news/redirects.json index b5e90a5d4..2ab4f0216 100644 --- a/docs/news/redirects.json +++ b/docs/news/redirects.json @@ -58,6 +58,7 @@ "/news/archie/1.42.0/": "/news/1.42.0/", "/news/archie/1.43.0/": "/news/1.43.0/", "/news/archie/1.44.0/": "/news/1.44.0/", + "/news/archie/1.44.1/": "/news/1.44.1/", "/news/archie/1.5.0/": "/news/1.5.0/", "/news/archie/1.6.0/": "/news/1.6.0/", "/news/archie/1.7.0/": "/news/1.7.0/", @@ -133,6 +134,7 @@ "/news/archied/1.42.0/": "/news/1.42.0/", "/news/archied/1.43.0/": "/news/1.43.0/", "/news/archied/1.44.0/": "/news/1.44.0/", + "/news/archied/1.44.1/": "/news/1.44.1/", "/news/archied/1.5.0/": "/news/1.5.0/", "/news/archied/1.6.0/": "/news/1.6.0/", "/news/archied/1.7.0/": "/news/1.7.0/", diff --git a/docs/news/releases.json b/docs/news/releases.json index b964f4f61..d3d5611bc 100644 --- a/docs/news/releases.json +++ b/docs/news/releases.json @@ -1,4 +1,9 @@ [ + { + "version": "1.44.1", + "date": "2026-09-29", + "body": "### archied\n\nTwo fixes to tasks that could not get past their workflow definition.\n\n- **Approving a task no longer parks it again.** A task requeued under a\n different workflow kept the previous run's definition pinned, so the worker\n refused to compile the dispatch — it named `feasibility` while the row named\n `implement` — and the task parked immediately, identically on every further\n approval, which left `decline` as the only working operator action.\n The daemon now re-pins whenever the pinned definition's id disagrees with the\n task's workflow. A pin that is present, digest-valid and id-consistent is\n still a strict no-op, so an operator's own definition override survives a\n dispatch unchanged.\n- **A shipped workflow definition now reaches an existing install.** A stored\n seed was consulted only for a resource the store did not already hold, so a\n document that changed in the build never reached a database an earlier\n release had seeded. For workflow definitions that is a total outage rather\n than a stale setting: the collection validates as one document, so a stored\n step type this build no longer has failed every task's pin, whatever workflow\n the task named — and the documented recovery, removing the resource and\n restarting, wrote nothing either, because the store answered the seed's known\n request ID from a history that outlives the resource. A seed now refreshes a\n kind it wrote the newest revision of and re-creates a resource that is gone,\n while an operator's own replacement is never undone.\n\n### archie-agent\n\nThe runtime image is rebuilt with this release and links the shared workflow\npackage carrying the definition-id helper above. Hosts that run agent\ncontainers need `docker compose pull agent` after updating to pick it up." + }, { "version": "1.44.0", "date": "2026-09-29",