Skip to content

No recovery path for schemas/<version> and compliance/<version> trees missing from the artifact CDN (3.0.27, 3.0.28) #8347

Closed

Description

@bokelley

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:

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,

  1. checks out tag v<version> (recovery logic itself must come from the current reviewed main, never from the tag),
  2. verifies the signed release tuple — sha256 plus a cosign identity bound to release.yml — exactly as recover-protocol-cdn.yml does,
  3. verifies that the committed dist/schemas/<v> and dist/compliance/<v> trees are byte-for-byte the schemas/ and compliance/ trees inside that signed tarball, so the cosign signature transitively covers every object it is about to publish,
  4. uploads only missing immutable objects (If-None-Match: *; an existing object must already match byte-for-byte, never an overwrite),
  5. 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

  1. added a commit that references this issue on Oct 20, 2026
    f5f9aed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions