Skip to content

Sync staged changes (2026-05-20, non-breaking only)#2770

Merged
vaishakdinesh merged 4 commits into
nextfrom
sync/staging-next-2026-05-20
May 20, 2026
Merged

Sync staged changes (2026-05-20, non-breaking only)#2770
vaishakdinesh merged 4 commits into
nextfrom
sync/staging-next-2026-05-20

Conversation

@vaishakdinesh
Copy link
Copy Markdown
Member

Codegen Sync: staging-next -> next

Synced 3 of 8 changed resources from staging-next as of 2026-05-20.

Source: origin/staging-next @ b5b4cc6
Base: origin/next @ 45bd3e2

Local Validation (all three gates pass)

Gate Command Result
Type check npx tsc --noEmit pass
Lint ESLINT_USE_FLAT_CONFIG=false npx eslint --ext ts,js . pass
Breaking changes ./scripts/detect-breaking-changes origin/next pass (exit 0)

Integrated Resources

Resource Type Summary
organizations feat add billing sub-resource (Billing -> Usage -> get method)
radar chore update codegen output
zero-trust chore update codegen output

Deferred: Breaking Changes (still unresolved)

These resources have spec-driven changes that affect SDK contract.
api-gateway and cache carry over from the previous sync; billing and
email-security are new this cycle.

Resource Change Notes
api-gateway discovery.operations.edit() removed Same as previous sync
cache originCloudRegions.create -> update (POST -> PUT) Same as previous sync
cache originCloudRegions.bulkEdit -> bulkUpdate Same as previous sync
cache originCloudRegions.edit removed Same as previous sync
billing usage.paygo endpoint URL changed: /billing/usage/paygo -> /paygo-usage SDK signature unchanged, but underlying API contract changed; defer until spec-owner confirms
email-security InvestigateListParams.action_log parameter removed Removes a query parameter from public type surface

Note on billing: this resource also adds a non-breaking usage.get method
(new endpoint GET /accounts/{account_id}/billable/usage). It is held back
along with the rest of the resource because the resource boundary is the
top-level directory. Can split into a non-breaking-only PR if you want
usage.get in sooner.

The local detect-breaking-changes script flagged email-security directly
(removed query param breaks old test). For billing, the script passes
because the SDK method signature is unchanged; the endpoint URL change was
caught by the surface analyzer (scripts/common/summarize-diff.ts).

Deferred: Codegen Regression (still unresolved)

billing is now fixed by the codegen team (Usage.paygo re-added plus a
new Usage.get method), so this list is shorter than before.

Resource Root Cause
addressing RegionalHostnames and Regions classes generated empty -- methods exist on next, stripped on staging-next, new tests still reference them

Shared Changes (codegen artifacts only)

  • .stats.yml -- spec hash bump
  • scripts/detect-breaking-changes -- updated test path list

Intentionally NOT touched:

  • .github/workflows/* -- human-owned
  • .release-please-manifest.json, CHANGELOG.md, package.json, src/version.ts -- release-please-bot owned
  • src/index.ts, src/resources/index.ts, root api.md -- no diff in this sync

Tracker: command-center/.local/sync-typescript-2026-05-20.md (in devstack)

@vaishakdinesh vaishakdinesh merged commit 7f48f70 into next May 20, 2026
10 checks passed
@vaishakdinesh vaishakdinesh deleted the sync/staging-next-2026-05-20 branch May 20, 2026 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant