✽ Sync staged changes#2710
Open
stainless-app[bot] wants to merge 148 commits into
Open
Conversation
* feat(queues): add queues metrics endpoint
* chore: skip failing tests for dns.records and workers.beta.workers - dns.records.scan_review: mock server returns invalid response data - dns.records.scan_list: mock server returns invalid response data - workers.beta.workers.create: HTTP 400 error from prism (missing required body properties) - workers.beta.workers.update: HTTP 400 error from prism (missing required body properties) Failures observed in both Python and TypeScript SDK test suites.
…rs.observability.telemetry * chore: skip failing tests for email_security.settings and workers.observability.telemetry - email_security.settings.allow_policies.edit: HTTP 422 from prism - email_security.settings.block_senders.edit: HTTP 422 from prism - email_security.settings.impersonation_registry.edit: HTTP 422 from prism - email_security.settings.trusted_domains.edit: HTTP 422 from prism - workers.observability.telemetry.keys: HTTP 400 from prism - workers.observability.telemetry.query: HTTP 400 from prism - workers.observability.telemetry.values: HTTP 400 from prism Failures observed in CI run 25132870851 on cloudflare-typescript PR #2743.
* chore: skip fraud.update test (HTTP 422 from prism) Failure observed in CI run 25171503153 on cloudflare-typescript PR #2746.
* feat(python): switch package manager from rye to uv
* feat(api): add zero_trust_device_deployment_groups resource * feat(api): add zero_trust_device_deployment_groups resource
…s to Security Center API * feat(SCTR): add audit log, classification, and context endpoints to Security Center API
* chore: skip failing Go SDK tests for workers bulk secret update Skip workers.scripts.secrets.bulk_update and workers_for_platforms.dispatch.namespaces.scripts.secrets.bulk_update. Both fail with HTTP 422 from prism due to bulk secret update request shape mismatch. Matches inline t.Skip() annotations in cloudflare-go sync PR cloudflare/cloudflare-go#4317.
…sources * feat(workers): adds Workers > Observability > Shared Queries resources
…n_restrictions endpoints * feat(email_security): add url_ignore_patterns and sending_domain_restrictions endpoints
* feat(dlp): add custom prompt topics endpoint Add `/dlp/custom_prompt_topics` endpoint.
* feat(resource_tagging): add summary endpoint mapping
stainless-app
Bot
force-pushed
the
staging-next
branch
from
b34e2e0 to
65beeea
Compare
* feat(api): add tenant custom nameservers resource mapping
Add Stainless config for tenant-level custom nameserver endpoints:
- get /tenants/{tenant_tag}/custom_ns
- create (post) /tenants/{tenant_tag}/custom_ns
- delete /tenants/{tenant_tag}/custom_ns/{custom_ns_id}
Ref: DNS-12922
…1810) * feat(api): use csam_scanner as top-level resource (TMD-1300) Replaces the original bot-authored structure (csam_scanner parent with third_party subresource pointing at non-existent /settings/csam_scanner paths) with a single top-level csam_scanner resource whose methods point at the real /settings/csam_scanner_third_party endpoint. This matches the structure already on the staging branch (via !922): client.zones.settings.csam_scanner.get(zone_id=...) client.zones.settings.csam_scanner.edit(zone_id=..., ...) Required because the csam_scanner path was removed from the OpenAPI spec in csam-config-service !453 (only csam_scanner_third_party is operational). Keeping the old structure would cause Stainless codegen to reference paths that don't exist in the production aggregate. * feat(api): add csam_scanner to SDK navigation listing Register csam_scanner in the Security section of the resources navigation so it appears in SDK client namespaces and generated docs. Ref: APIX-798 * feat(api): add CSAM scanner settings endpoint mappings Map csam_scanner and csam_scanner_third_party zone settings endpoints to SDK resources with get and edit methods. Ref: APIX-798
* fix(oauth): Updating action, adding rotate secret * feat(oauth): Move oauth scopes endpoint to standalone * feat(oauth): Add SDK support for oauth clients and scopes
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.
This PR was automatically created to sync staged changes from Stainless to the next branch. New commits will be added to this PR as they are staged.