Incident Dossier

Asset Cache Bust On Stale Rev

A static-asset helper builds cache-busted URLs from a build revision. The revision is captured at module-import time as a constant, then threaded through a manifest builder and finally into the URL helper. By the time the deploy pipeline sets the real revision, the helper has already baked in the dev value and every fresh deploy serves stale asset URLs.

Initial failing signalfresh BUILD_ID does not reach the cache-busted URLExpected behavior: asset('/app.js', { BUILD_ID: 'abc123' }) === '/app.js?v=abc123' · actual behavior: asset('/app.js', { BUILD_ID: 'abc123' }) === '/app.js?v=dev'

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Trace how the revision flows from process.env through the manifest into the URL.
Notice which step captures the value at import time vs at call time.
Confirm the failure when a fresh BUILD_ID is supplied at call time.
Make the smallest correction so the revision is read at the moment of the call.

Focus Mode

Start

src/build.js
src/manifest.js
src/assets.js

Likely area

src/build.js
src/manifest.js
src/assets.js

Challenge Coach

Hints reveal broad direction first, then narrow toward the suspect path without showing hidden tests or exact solution code.

TopicDeployment

DifficultyHard

Est. time25 min

Workspacepreparing

Explorer

Loading files

Evidence Map

Failing signal loaded from challenge API
Workspace files loaded from workspace API
Results rendered only after API run/submit

Autosaved

workspace

Outputread-onlyready$ prepare workspace

Preparing workspace