Skip to content

Codegen sync: staging-next -> next (2026-05-21)#2727

Open
musa-cf wants to merge 16 commits into
nextfrom
sync/staging-next-2026-05-21
Open

Codegen sync: staging-next -> next (2026-05-21)#2727
musa-cf wants to merge 16 commits into
nextfrom
sync/staging-next-2026-05-21

Conversation

@musa-cf
Copy link
Copy Markdown
Contributor

@musa-cf musa-cf commented May 22, 2026

Codegen Sync: staging-next -> next

Synced 15 resources from staging-next as of 2026-05-21.

Integrated Resources

Resource Type Summary
addressing chore remove regional_hostnames sub-resource
billing feat add usage get endpoint, 2 new types
custom_certificates chore update create/edit params
dls feat add dls resource with regions, regional_services
email_security chore update investigate params
email_sending chore update send params
intel chore update sinkhole types
load_balancers chore remove monitor_groups
organizations feat add billing sub-resource
radar chore remove bgp ips, update http params
realtime_kit feat add 3 new types, update meetings/apps
secrets_store feat add store get response type
spectrum chore update app params and response types
workers feat add observability queries, update scripts
zero_trust feat add server sync, update identity providers

Excluded Resources

None -- all 15 resources passed validation.

Shared Changes

  • Updated _client.py, _base_client.py, _version.py
  • Updated api.md, .stats.yml, pyproject.toml, uv.lock
  • Updated CI workflows and changelog

Validation

  • pyright: 2 pre-existing errors only (httpx_aiohttp import in _base_client.py)
  • ruff: all checks passed
  • working tree clean

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