Repository navigation
chore(release): prepare AdCP 3.3.0-rc.0 - #9050
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
Ladon verdict: Approve
Approve — RC promotion marker is clean.
Reviewed the sole changed file .changeset/rc-promotion.json (66 additions, machine-generated by promote-release-candidate.mjs). Verified: from/to match package.json (3.3.0-beta.6) and the correct RC target; all 15 pendingChangesets entries present, sorted in JS code-unit order, and every sha256 matches the on-disk changeset (15/15); file shape matches prepareRcPromotion output. No protocol/schema/docs/dist surface touched — no immutable-artifact, oneOf, changeset-scope, or 3.1.x concerns apply.
No Critical/High/Medium findings. No gated paths (gated_paths: false), no high-risk flag, no no-auto-approve team match, no prior decision. Decision table rows 1–8 do not fire; falls through to row 9 → approve. (review_decision is REVIEW_REQUIRED, but row 2 only gates on gated_paths, which is false here.)
* docs(reference): describe #8915's reserved-word-safe enum replacements in the rc.0 docs #8915 (f4899aa) merged after the rc.0 marker. It adds a replacement for six enum positions that collide with SDK target languages and deprecates the originals: pass to passed (binary-verdict, local_verdict, the registry feed's compliance tracks status), global to all (RATE_LIMITED scope), and name to full_name (signal onboarder match_keys, on the definition and the enrichment). Both spellings are valid through 3.x, and 4.0 removes the originals. Send a replacement only to a peer served 3.3 or later; published files keep the original. Add it to the rc.0 rows, the release-notes rc.0 bullet, status line and deprecations, What's new, migration checklist row 61, a migration section with old and new values, the send-only-to-3.3-peers table, and the deprecations intro. #8915's v4-compatibility text is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore(release): refresh the 3.3.0-rc.0 marker for #8915 #8915 (reserved-word-enum-replacements.md) merged after the rc.0 marker (#9050), so the Release run's promote check would reject #9009 with "Pending changesets do not match the reviewed RC promotion marker". Regenerate .changeset/rc-promotion.json with npm run promote:rc -- --prepare. It folds all 17 pending changesets into 3.3.0-rc.0, each with its sha256: the 15 #9050 listed, reserved-word-enum-replacements.md, and this PR's rc0-docs-reserved-word-enums.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This PR prepares AdCP 3.3.0-rc.0. It only records state: one file,
.changeset/rc-promotion.json, written bynpm run promote:rc -- --prepareon main41d269f09f(#8883).3.3.0-beta.6→3.3.0-rc.0.Merge order:
--prepareagain.3.3.0-rc.0.merge-baseequals the main tip;3.3.0-rc.0;pre.jsonreads{"mode":"pre","tag":"rc"};3.3.0-rc.0;Not in rc.0: #8854,
metric_idwithdrawal /evaluator, still in review. The release docs say so.Hooks: the commit used
HUSKY=0and the push skipped the local storyboard matrix. The change is a single generated JSON state file; CI is the gate.🤖 Generated with Claude Code