fix(registry): bump updated-at to bust stale tarball caches (reach the #269 file manifest fix)#271
Merged
pawellisowski merged 1 commit intoJun 26, 2026
Conversation
…#269 file manifest fix) #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.
pawellisowski
deleted the
fix/registry-index-bump-busts-stale-file-manifest
branch
pawellisowski
added a commit
that referenced
this pull request
Jun 26, 2026
…backs (#270) Ships the residual tarball-cache staleness fixes merged since v0.81.0: - #272 (#270): 1h TTL on the agent-install tarball cache so an in-archive manifest change that leaves registry-index.json byte-identical self-heals within an hour, with graceful fallback to a prior index-consistent cache on offline/corrupt/raced refreshes. - #271: bump registry-index.json updated-at to bust warm caches for the #269 file agent.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Bump
registry-index.jsonupdated-at(2026-06-18 → 2026-06-26). Data-only, one line.Why
#269 flipped
_core/filestatus: planned → availableinside the rollingmain.tar.gzbut leftregistry-index.jsonunchanged. The agent-install tarball cache is keyed onIndex::snapshot_fingerprint()(a hash of registry-index.json), so the key never rotated — users who cachedmain.tar.gzbetween #257 (06-18) and #269 (06-25) keep installing the stalefilemanifest (status: planned), andaware app runthen rejects a runnablefile/writenode withE_APP_AGENT_UNAVAILABLE.Bumping
updated-atis the documented "manual refresh lever" (cli/src/registry/index.rs): it rotates the fingerprint so every stale tarball cache busts on the next install. The index is fetched live frommainwith a 1h TTL, so this propagates to all users within the hour — no binary release needed. After it lands,aware agent install fileyieldsstatus: available.This unblocks a downstream floless.app feature (steel-model BOM export nodes use
file/write).Verification
aware agent reindex --check→ ✓ up to date (the catalog carries its own timestamp; the index bump doesn't stale it).install/registry.rs:48-63+registry/index.rs snapshot_fingerprint+registry/fetch.rs(live sourceraw.githubusercontent.com/.../main/registry-index.json, 1h TTL).status: availablefrom freshmain; this bump achieves the same bust systematically.Review note
Data-only registry refresh-lever bump (no code) — there is nothing for a code reviewer to assess; treating Codex review as N/A for this one-line operational change.
Refs #270 (the systemic fix: auto-bump on manifest change / TTL the tarball cache).