Repository navigation
Conversation
The 3.3.0-rc.1 Version Packages merge registered rc.1 in published-versions.json, but release run 44300240363 quarantined it at the provenance gate and #9090 marked it unpublished. The manifest's own policy registers a version only once release provenance is available. Because every published_versions entry anchors its schema and compliance bundle in the runtime image, rc.1 added ~170 MiB and pushed the image to 7439 MiB, over the 7424 MiB cap (deploy run 44353722716). Every deploy from main fails the image-size check until it comes back under. Drop rc.1 from published_versions. Its committed dist bytes, the supersession marker and the pending changeset set are unchanged, so the release-supersession gate still matches. No SDK on a tracked npm tag bundles rc.1 (check-published-compliance-versions passes). compliance-authored-tool-gates graded its synthetic run as package.json's version. Hosted grading resolves pinned storyboards only for published versions, so grade as the channel's newest published version instead; that is rc.0 today and the new candidate once Version Packages cuts it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Every production deploy from
mainfails the image-size gate:(deploy run 44353722716, attempt 2, head
859ea919be)b5ac0e1bf7(live)5eb0b201f4859ea919be(after #9073 and #9090)#9073 registered
3.3.0-rc.1instatic/compliance/published-versions.json. Every entry there anchors that version's schema and compliance bundle in the runtime image. Release run 44300240363 quarantined rc.1 at the provenance gate, and #9090 marked it unpublished, but it stayed in the manifest. The manifest's own policy registers a version only once release provenance is available.What
3.3.0-rc.1frompublished_versions. The pruner then leaves its ~170 MiB of schemas and compliance out of the image. Its committeddist/bytes, the supersession marker, and the pending changeset set don't change, so therelease.ymlsupersession gate (which comparesdist/schemas,dist/complianceanddist/protocolfor rc.1, plus the exact pending changesets) still matches. No changeset is needed: this changes no protocol content.tests/addie/compliance-authored-tool-gates.test.tsgraded its synthetic run aspackage.json's version, which is still3.3.0-rc.1. Hosted grading resolves pinned storyboards only for published versions (pinnedStoryboard()→hostedComplianceTarget()), so the optional-tool "not applicable" disposition was lost and 8 cases scoredpartial. The test now grades as the channel's newest published version: rc.0 today, and rc.2 once Version Packages registers it.Production is unaffected by that grading path: hosted runs are stamped with a hosted target's version, and production (
b5ac0e1bf7) predates rc.1, so no run was ever graded at rc.1.Not sufficient on its own
rc.2 (#9091) adds its own ~145–175 MiB, so after it merges the image is back at about 7440 MiB. At least one more version has to leave the image. The measurements and options are in the runtime-image-size proposal. The largest single lever is the
schemas/bundled/+schemas/mcp/subtrees: about 135 of each version's ~145 MiB, and ~5.6 GiB across all 72 retained versions.Verification
node scripts/check-published-compliance-versions.cjs: the manifest is current for npm tagsadcp-3.0,adcp-3.1,adcp-3.2,latest,rc. No tracked SDK bundles rc.1.runtimeArtifactManifest()no longer retains rc.1 (72 schema and 71 compliance versions).hosted-compliance-version,hosted-run-test-kit,storyboards: 94/94.compliance-authored-tool-gates: 66/66. Pre-commit server suite: 1284/1284.🤖 Generated with Claude Code