Skip to content

fix(cli): bypass stale cache on tag-based registry lookup#648

Merged
miguel-heygen merged 1 commit intomainfrom
fix/registry-cache-bust
May 6, 2026
Merged

fix(cli): bypass stale cache on tag-based registry lookup#648
miguel-heygen merged 1 commit intomainfrom
fix/registry-cache-bust

Conversation

@miguel-heygen
Copy link
Copy Markdown
Collaborator

Summary

  • hyperframes add html-in-canvas (tag-based bulk install) was failing because the tag fallback path reused the same 24h cached registry manifest as single-item lookups
  • When new blocks are added to the registry, the stale cache returns an incomplete item list, so tag resolution finds zero matches and reports "not found"
  • The fix passes skipCache: true in the tag fallback path so it always fetches the latest manifest

Changes

  • remote.ts: fetchRegistryManifest accepts optional skipCache flag
  • resolver.ts: ResolveOptions gains skipCache, threaded through listRegistryItems
  • add.ts: tag fallback calls resolveItemsByTag with skipCache: true

Test plan

  • All 257 CLI tests pass
  • npx hyperframes add html-in-canvas installs 7/7 blocks after cache clear
  • Build, lint, format all clean

The add command's tag fallback (e.g. `hyperframes add html-in-canvas`)
uses the same 24h cached manifest as single-item lookups. When new items
are added to the registry, the stale cache returns an incomplete item
list, causing tag resolution to find zero matches.

Pass skipCache: true in the tag fallback path so it always fetches the
latest manifest from the registry.
@miguel-heygen miguel-heygen merged commit 35e71cb into main May 6, 2026
27 of 28 checks passed
@miguel-heygen miguel-heygen deleted the fix/registry-cache-bust branch May 6, 2026 17:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant