fix: add MF remote cache invalidation via buildHash and manifest freshness

[swalker326]

Summary

• Add optional buildHash field to ZephyrManifest interface for cache-busting
• Compute buildHash (SHA-256 of sorted remote_entry_urls) during manifest creation
• Runtime plugin: always fetch fresh manifest with cache: 'no-cache' + timestamp query param for SSR compatibility
• Runtime plugin: append ?v=<buildHash> to remote entry URLs so MF runtime treats each new build as a distinct remote
• Skip buildHash on session storage overrides (local dev)

Related PRs (common branch fix/mf-cache-invalidation-live-reload)

• zephyr-panel: bypassCache: true on chrome.tabs.reload()
• zephyr-mono: Worker engine Cache-Control differentiation + ETag
• zephyr-cloud-io: WebSocket message enrichment with snapshot_id

Problem

Module Federation's runtime caches loaded remotes by URL. When a new version is deployed, the remote entry URL doesn't change (same path, new content), so MF serves the cached old version. The runtime plugin's in-memory manifest cache (window.__ZEPHYR_MANIFEST_CACHE__) also prevents re-fetching updated manifests.

Changes

File	Change
libs/zephyr-edge-contract/src/lib/zephyr-manifest.ts	Add buildHash?: string to ZephyrManifest
libs/zephyr-agent/src/lib/transformers/ze-create-manifest.ts	Compute buildHash from dependency URLs (skipped for standalone apps)
libs/zephyr-xpack-internal/src/xpack-extract/runtime-plugin.ts	cache: 'no-cache' + ?_t= on manifest fetch, ?v=buildHash on remote URLs, always re-resolve remotes

Backward Compatibility

• buildHash is optional — old manifests without it still work (no query param appended)
• cache: 'no-cache' still allows 304 responses — no performance regression
• Session storage overrides (local dev) are unaffected

[nx-cloud]

🤖 Nx Cloud AI Fix Eligible

An automatically generated fix could have helped fix failing tasks for this run, but Self-healing CI is disabled for this workspace. Visit workspace settings to enable it and get automatic fixes in future runs.

_{To disable these notifications, a workspace admin can disable them in workspace settings.}

---

View your CI Pipeline Execution ↗ for commit 86e0c52

Command	Status	Duration	Result
nx affected -t build --skipRemoteCache	❌ Failed	45s	View ↗
nx affected -t test	✅ Succeeded	1m 41s	View ↗
nx affected -t lint	✅ Succeeded	5s	View ↗
nx affected --exclude=!libs/** -t build --skipR...	✅ Succeeded	14s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-02-11 13:26:12 UTC