verify-hosting-headers.ts passed the serviceWorker probe only when
cache-policy.json said `enabled: false` AND dist had no worker script, so no
configuration let a supported ACTIVE build through the hosting gate. The
probe now follows the static selection: ACTIVE requires exactly the selected
`service-worker.js` at the dist root; null / REMOVE_REGISTRATION /
PURGE_OWNED_RESOURCES still reject any worker script. The now-unused
`serviceWorker.enabled` policy flag is removed; the artifact keeps the same
`serviceWorker`/`enabled` probe key.
RED (ACTIVE build from the previous commit, `node scripts/verify-hosting-headers.ts`):
Hosting cache/content-type/security header verification failed. exit=1
{ surface: serviceWorker, header: enabled, expected: false, observed: true, passed: false }
GREEN: same ACTIVE build -> PASS exit=0 (expected: true, observed: true);
default build -> PASS; default build + stray dist/service-worker.js -> exit=1
(reason "dist worker scripts: service-worker.js");
tests/unit/hosting-probe.test.ts 13 passed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
33 lines
806 B
JSON
33 lines
806 B
JSON
{
|
|
"schemaVersion": 1,
|
|
"surfaces": {
|
|
"index": {
|
|
"path": "/",
|
|
"cacheControl": "no-cache",
|
|
"contentTypes": ["text/html"],
|
|
"securityHeaders": true
|
|
},
|
|
"runtimeConfig": {
|
|
"path": "/config.json",
|
|
"cacheControl": "no-store",
|
|
"contentTypes": ["application/json"],
|
|
"securityHeaders": true
|
|
},
|
|
"releaseManifest": {
|
|
"path": "/release-manifest.json",
|
|
"cacheControl": "no-store",
|
|
"contentTypes": ["application/json"],
|
|
"securityHeaders": true
|
|
},
|
|
"hashedAsset": {
|
|
"pathPattern": "/assets/*",
|
|
"cacheControl": "public, max-age=31536000, immutable",
|
|
"contentTypes": ["text/javascript", "application/javascript"],
|
|
"securityHeaders": false
|
|
},
|
|
"sourceMap": {
|
|
"public": false
|
|
}
|
|
}
|
|
}
|