Repository navigation
Description
Problem
schemas/3.0.27/, schemas/3.0.28/, compliance/3.0.27/ and compliance/3.0.28/ were never published to the artifact R2 bucket, even though v3.0.27 and v3.0.28 are tagged, released, and carry committed dist/ trees. The protocol tuples for both versions are present (protocol/3.0.28.tgz* was recovered by dispatching recover-protocol-cdn.yml on 2026-10-16); only the schema and compliance trees are missing.
This is worse than a 404. The CDN worker's resolvePinnedFallback resolves a pinned semver with no published directory to the nearest release at-or-below it on the same line, so today:
$ curl -s https://adcontextprotocol.org/schemas/3.0.28/index.json | head -4
{
"$schema": "http://json-schema.org/draft-07/schema#",
"$id": "/schemas/3.0.26/index.json",
...
"adcp_version": "3.0.26",
A consumer that pins 3.0.28 gets 200 OK with 3.0.26 bytes and no error. /compliance/3.0.27/index.json and /compliance/3.0.28/index.json do the same. The only outward signal is cache-control: public, no-cache, must-revalidate instead of the immutable policy an exact pinned hit gets.
Knock-on effect (#8318 / #8324): scripts/build-schema-discovery-pointers.cjs refuses to advertise a release whose schemas/<version>/index.json object it cannot confirm, so the published schemas/index.json pins v3.0 to 3.0.26 and every deploy logs ::warning title=Schema versions missing from the CDN::3.0.28, 3.0.27 ... Recover those releases per RELEASING.md.
Why there is no fix today
RELEASING.md tells that warning's reader to "recover those releases", but no workflow can. As RELEASING.md states: "The stable-only recover-protocol-cdn.yml recovers four protocol files, not schemas/compliance and not RC releases."
The other publication paths are correctly closed to this:
release.ymlpublishes only the version in the current checkout'spackage.json;check-release-state.cjs committedrequires the local, current-tested and original committed package versions to be equal, so it cannot write a historical version.backfill-cdn-artifacts.sh --latest-only(routine deploy) excludes every semver path.- Live unscoped bulk backfill is disabled on purpose (fix(release): forward-port 3.1.22/3.1.23 artifacts and hosted discovery #7507 / fix(release): fence publication and recover superseded releases #7510).
So the gap is permanent without a new, explicitly authorized path.
Ask
Build a safe recovery path, designed to RELEASING.md's publication-authority model: a maintainer workflow_dispatch that, for an exact released stable version,
- checks out tag
v<version>(recovery logic itself must come from the current reviewedmain, never from the tag), - verifies the signed release tuple —
sha256plus a cosign identity bound torelease.yml— exactly asrecover-protocol-cdn.ymldoes, - verifies that the committed
dist/schemas/<v>anddist/compliance/<v>trees are byte-for-byte theschemas/andcompliance/trees inside that signed tarball, so the cosign signature transitively covers every object it is about to publish, - uploads only missing immutable objects (
If-None-Match: *; an existing object must already match byte-for-byte, never an overwrite), - verifies the public CDN then serves those objects byte-exact — including that they resolve as an exact pinned hit rather than another silent fallback,
and fails closed on any mismatch. Tests.
No RC releases, no mutable aliases, no deletions, no root discovery pointers (those stay with the deploy path, per #8318).
Once merged, the dispatches to recover 3.0.27 and 3.0.28 need maintainer approval and execution.
Activity
fix(release): recover a release's schema and compliance trees on the …