Skip to content

Conversation

@stainless-app
Copy link
Contributor

@stainless-app stainless-app bot commented Jan 26, 2026

Automated Release PR

6.0.0-beta.2 (2026-01-27)

Full Changelog: v6.0.0-beta.1...v6.0.0-beta.2

Features

  • feat(api): add AI Gateway Dynamic Routing endpoints (5cb758b)
  • feat(fraud): public docs for fraud API (dac4aa5)
  • refactor(terraform): restructure origin_tls_client_auth to peer subresources (89f79e9)

Bug Fixes

Chores

  • api: update composite API spec (18f7f29)
  • api: update composite API spec (15c3924)
  • api: update composite API spec (ffa2c6c)
  • internal: codegen related update (72d9dfb)
  • internal: codegen related update (cb76fc9)

This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions

Chris Thorwarth and others added 11 commits November 18, 2025 16:57
* feat(fraud): public docs for fraud API
… subresources

* fix: add backward-compatible methods for origin_tls_client_auth

Adds deprecated parent-level methods (list, get, create, delete) to maintain
backward compatibility with existing SDK users while preserving the clean
cache-style resource structure.

Changes:
- Add 4 deprecated methods at parent level pointing to zone cert endpoints
- Methods generate client.OriginTLSClientAuth.New/List/Get/Delete() paths
- Deprecation messages guide users to zone_certificates.* subresource
- Zero breaking changes - existing SDK code continues to work
- New explicit paths available at ZoneCertificates.* and HostnameCertificates.*

This follows the proven KV namespace dual-path pattern (lines 2730-2752)
where the same endpoint generates methods at both parent and child levels.

Related: SECENG-12971

* refactor(terraform): restructure origin_tls_client_auth to peer subresources

Restructure origin_tls_client_auth to have all 4 terraform resources as sibling subresources:
- zone_certificates → authenticated_origin_pulls_certificate
- hostnames → authenticated_origin_pulls
- hostname_certificates → authenticated_origin_pulls_hostname_certificate
- settings → authenticated_origin_pulls_settings

Add id_property annotations to all CRUD methods.

Closes SECENG-12971, SECENG-12970, SECENG-13210
Comment on lines +10 to +36
runs-on: 'ubuntu-latest'
name: detect-breaking-changes
if: github.repository == 'cloudflare/cloudflare-typescript'
steps:
- name: Calculate fetch-depth
run: |
echo "FETCH_DEPTH=$(expr ${{ github.event.pull_request.commits }} + 1)" >> $GITHUB_ENV

- uses: actions/checkout@v6
with:
# Ensure we can check out the pull request base in the script below.
fetch-depth: ${{ env.FETCH_DEPTH }}

- name: Set up Node
uses: actions/setup-node@v3
with:
node-version: '20'
- name: Install dependencies
run: |
yarn install

- name: Detect breaking changes
run: |
# Try to check out previous versions of the breaking change detection script. This ensures that
# we still detect breaking changes when entire files and their tests are removed.
git checkout "${{ github.event.pull_request.base.sha }}" -- ./scripts/detect-breaking-changes 2>/dev/null || true
./scripts/detect-breaking-changes ${{ github.event.pull_request.base.sha }}

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}

Copilot Autofix

AI 2 days ago

  • In general, fix this by adding an explicit permissions: block that grants only the minimal scopes required by the job. This can be defined at the workflow root (applies to all jobs) or within the specific job.
  • For this workflow, the visible steps only require reading repository contents. There is no evidence of any operation that needs write access (no pushes, no issue/PR mutations, etc.). The single best fix is to add permissions: contents: read at the job level for detect_breaking_changes. This documents the intent and prevents the job from inheriting potentially broader default permissions.
  • Concretely, in .github/workflows/detect-breaking-changes.yml, modify the detect_breaking_changes job definition (around line 9–13) to introduce a permissions: block between name: and if: (or between any job-level keys, as long as indentation is correct).
  • No new methods, imports, or other definitions are needed; this is purely a YAML configuration change.
Suggested changeset 1
.github/workflows/detect-breaking-changes.yml

Autofix patch

Autofix patch
Run the following command in your local git repository to apply this patch
cat << 'EOF' | git apply
diff --git a/.github/workflows/detect-breaking-changes.yml b/.github/workflows/detect-breaking-changes.yml
--- a/.github/workflows/detect-breaking-changes.yml
+++ b/.github/workflows/detect-breaking-changes.yml
@@ -9,6 +9,8 @@
   detect_breaking_changes:
     runs-on: 'ubuntu-latest'
     name: detect-breaking-changes
+    permissions:
+      contents: read
     if: github.repository == 'cloudflare/cloudflare-typescript'
     steps:
       - name: Calculate fetch-depth
EOF
@@ -9,6 +9,8 @@
detect_breaking_changes:
runs-on: 'ubuntu-latest'
name: detect-breaking-changes
permissions:
contents: read
if: github.repository == 'cloudflare/cloudflare-typescript'
steps:
- name: Calculate fetch-depth
Copilot is powered by AI and may make mistakes. Always verify output.
* feat(api): add AI Gateway Dynamic Routing endpoints
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--cloudflare branch from f396455 to 4909d66 Compare January 27, 2026 01:08
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--cloudflare branch from 4909d66 to 0e0e835 Compare January 27, 2026 12:14
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--cloudflare branch from 0e0e835 to e11a06e Compare January 27, 2026 20:32
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--cloudflare branch from e11a06e to ea7ea04 Compare January 27, 2026 22:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants