Repository navigation
sync-alphalib-2026-10-07: Robot schemas and SDK pack compatibility - #539
Merged
Merged
Conversation
kvz
changed the title
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
1 participant
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.
Keep the shared alphalib graph consistent across all nine configured consumers after API2 #9507, without exporting repo-only dependencies or silently changing SDK response compatibility.
Adds GOOGLE_STORE_ACCESS_DENIED and DAM_STORAGE_UNAVAILABLE to the SDK-owned known error inventory, refreshes Robot schemas/model choices and the Google seed primitive, and retains the internal Save JSON owner boundary. Adapts pack fingerprint parsing to npm 12 package-keyed JSON while keeping prior layouts supported. Includes patch changesets for node, transloadit, MCP, types and zod.
Validation: full unit/check/verify chains, Zod v3/v4 public type equality, clean-output generators, pack and explicit-baseline package parity pass. The reviewed integrity-verified transloadit 5.2.0 baseline keeps entry points, exports, dependency manifests and the Node 20.10 floor unchanged. Numeric State/XPSubject, repeated dates, null upload extensions and future public errors are deliberately in a separate breaking SDK PR, as Kevin requested. No package was released.
All nine reconciled trees passed the built-in parity guard before publication. No extra checkout/worktree or .env change was made. The stale-checkout dry-run correction and Content publication repin are separate PRs.
Companion sync PRs:
The separately requested breaking response corrections are in #540, stacked on this branch. They use major changesets for node/transloadit/types/zod and pre-1.0 minors for MCP/notification relay; no package is published here.