From d59b65e75372f0e72232cc45793ed0a84647aa11 Mon Sep 17 00:00:00 2001 From: Pawel Date: Fri, 26 Jun 2026 09:10:51 +0200 Subject: [PATCH] fix(registry): bump updated-at to bust stale tarball caches (reach the #269 file manifest fix) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit #269 changed `20-agents/_core/file/manifest.yaml` (status: planned → available) INSIDE the rolling `main.tar.gz`, but did not touch `registry-index.json`. The agent-install tarball cache is keyed on `Index::snapshot_fingerprint()` (a hash of registry-index.json), so a manifest change that leaves the index unchanged never rotates the key — users who cached `main.tar.gz` between #257 (2026-06-18) and #269 (2026-06-25) keep getting the STALE `file` manifest (status: planned). `aware app run` then rejects an actually-runnable `file/write` node with E_APP_AGENT_UNAVAILABLE. Bumping `updated-at` is the documented "manual refresh lever" (registry/index.rs): it rotates the fingerprint so every stale tarball cache busts on the next install (index is fetched live from main with a 1h TTL), and `file` installs as status: available. Data-only; `aware agent reindex --check` stays green (the catalog carries its own timestamp). Systemic fix tracked separately. --- registry-index.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/registry-index.json b/registry-index.json index 32dda2f4c..f12fcaf28 100644 --- a/registry-index.json +++ b/registry-index.json @@ -1,6 +1,6 @@ { "version": "1.0", - "updated-at": "2026-06-18T13:49:07Z", + "updated-at": "2026-06-26T08:00:00Z", "agents": { "tekla": { "versions": {