Version Packages (rc)

[bokelley]

Bumps the prerelease package from 3.1.0-rc.9 to 3.1.0-rc.10 and updates the schema registry version metadata.

Adds the generated 3.1.0-rc.10 schema, compliance, and protocol tarball artifacts, including the checksum sidecar.

Updates the changelog and prerelease bookkeeping for the changesets merged since rc.9.

Validated with npm run version, npm test, npm run build, precommit checks, and pre-push storyboard matrices for current source plus 3.0 compatibility.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
adcp	🟢 Ready	View Preview	Jun 7, 2026, 9:18 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[aao-release-bot]

Mechanical changesets release PR — 3.1.0-rc.9 → 3.1.0-rc.10. Correct because the versioning surface (CHANGELOG + pre.json + regenerated dist artifacts) is exactly what the changesets release flow is supposed to move, and nothing else moves with it.

Things I checked

• Single commit fb7ce8aa4 "Version packages" — the canonical bot commit, no extra work smuggled in.
• package.json version 3.1.0-rc.9 → 3.1.0-rc.10; the version script confirms the pipeline (changeset version → build:schemas --release → build:compliance --release → build:protocol-tarball --release → sign:protocol-tarball). Version metadata is internally consistent: package.json, CHANGELOG top section, pre.json tag: rc, and the dist/.../3.1.0-rc.10/ paths all agree.
• .changeset/pre.json: +18 consumed changeset slugs, still in pre mode — consistent with pre-mode behavior (changeset .md files are not deleted until pre-exit).
• CHANGELOG rc.10 section aggregates already-reviewed changesets, each with commit lineage. The wire-touching entries (postal targeting rework 72b79ac refs #5383, build_creative paused 313e3a9, recipe_hash fa64db9) landed in their own PRs with their own changesets — this PR publishes, it does not author.
• a4a51bc (current main tip, build_creative async webhooks) is captured in the rc.10 changelog — the release isn't missing the latest source change.
• No static/schemas/source/** edit: 1,031,975 additions against 5 deletions is purely-additive generated output (the new dist/compliance/** and dist/protocols/** rc.10 trees plus checksum sidecar), not source modification.

Minor nits (non-blocking)

1. A million-line diff whose load-bearing surface is 67 lines (49 in CHANGELOG, 18 in pre.json). Everything else is machine-generated and reviewed at the source PRs. Noted, not a concern — it's the nature of committing release artifacts.

LGTM.