Repository navigation
Add missing TypeScript Official API round-2 beta counterparts - #360
Merged
Merged
Conversation
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
Comment |
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.
Summary
Adds the confirmed missing TypeScript counterparts for Official API round-2 betas: native catalog cache reads/sync, native marketing status, Official group picture upload, incoming carts, identity/lifecycle event types, readiness/send errors, and Platform webhook batching with signed batch decoding. Existing Graph, contact, Linked Devices group and history methods are reused.
The audit checked main and exact open heads #345, #346, #347, #348, #350, #355, #357, #358 and #359. No SDKS-owned branch was changed.
Impact
packages/typescript/src,examples/official-api-round2/index.ts, focused wire and signed-envelope testsdocs/official-api-round2.mdcontracts/official-api-round2.jsonpins all six merge SHAs, spec/release hashes andpublished:false; release gate consumes itNo impact table
Verification
Node 24.15.0: 148 files / 1,560 tests passed; typecheck (including the new example), workspace builds, lint, format, strict coverage, release-evidence tests, functions/name checks and production dependency audit passed. Existing lint directives emit two warnings. The final full suite passed again after isolating readiness types to avoid overlap with SDKS-owned branches. Read-only merge-tree checks are clean against the pinned #348, #355 and #357 heads.
Physical SDK package consumer tests pass. HTTP, multipart and webhook tests use synthetic fixtures. No live Meta, hosted receiver, regional deployment or staging/production acceptance was exercised. Exact-head CI 39565150051 passes on Node 20 and 22 at
f9937116b17f9962de8a3eb632c44d0399b05002.All candidate workflow selectors are GitHub-hosted
ubuntu-latest; there are no ci-1/self-hosted selectors. Workflow and dependency/lock inputs are unchanged. The monorepo CI push hold therefore does not cover this SDK push.Session provenance and UI evidence
Registration: purpshell-t3-codex. Agent: Codex / gpt-6.1-sol. Delegated task:
oa-p-sdk-cli-20261021. Selected raw visible excerpts are retained locally inside a dedicated monorepo worktree; full delegated capture and a published checkpoint are unavailable. The recorder expects the older T3 projection, and root has held monorepo pushes. No graphical UI changed; wire fixtures and compile-checked examples provide client evidence.Rollout and rollback
Targets SDK main at
d2c5b3dfe4b13dee6d7a07b96df213e47ef8130a. Contract source is accepted backend9bb1e2ed92d8b4a07ff727f8e7ae185498f0868f, also compared with later devdafb7cb4e4efbcdcbd04af206f1ef6d47c209379. Per-item authoritative merge pins remain separate.These are flagged betas.
feature_unavailableremains a normal typed error; Hybrid groups never fall back to Official. Keep the PR draft until coordinator gates are resolved. Do not publish from this candidate: full release-pin reconciliation and matching staging acceptance precede prereleases; production acceptance precedes stable publication. No API contract date, flag or enrollment is advanced.Revert the client additions to roll back. The single-event parser remains available. A client revert does not undo provider effects or sealed backend batches.