Skip to content

Conversation

stainless-app[bot]
Copy link
Contributor

@stainless-app stainless-app bot commented Aug 22, 2025

Automated Release PR

5.0.0 (2025-10-22)

Full Changelog: v4.3.1...v5.0.0

Features

  • chore(abuse): rename path parameter (dd0b6fb)
  • docs(zero_trust_gateway_policy): add /rules/tenants endpoint to Gateway API docs (3c18fd3)
  • feat: add connectivity directory service APIs to openapi.stainless.yml (fc06837)
  • feat: SDKs for Organizations and OrganizationsProfile (3c3adc5)
  • feat(api): add mcp portals endpoints (70e068e)
  • feat(radar): add new group by dimension endpoints; deprecate to_markdown endpoint (845fba2)
  • fix(ai): rename duplicate parameter in the to_markdown subresource (e107db1)
  • fix(api): RAG-286: Add to_markdown subresource to AI resource (73fa6b1)
  • fix(content_scanning): content scanning terraform resource (16983e5)

Bug Fixes

  • do not set headers with default to omit (7b7b62f)

Chores

  • api: update composite API spec (5f5caef)
  • api: update composite API spec (5d19869)
  • api: update composite API spec (541c9fb)
  • api: update composite API spec (ba5b5fc)
  • api: update composite API spec (7baa51c)
  • api: update composite API spec (53d59f4)
  • api: update composite API spec (25d603f)
  • api: update composite API spec (9fd6645)
  • api: update composite API spec (19d1d96)
  • api: update composite API spec (f9160a4)
  • api: update composite API spec (c686a51)
  • api: update composite API spec (412ed20)
  • api: update composite API spec (119f889)
  • api: update composite API spec (65382bf)
  • api: update composite API spec (b3a3cf6)
  • api: update composite API spec (c78ef5e)
  • api: update composite API spec (71a023c)
  • api: update composite API spec (3805db3)
  • api: update composite API spec (c882cba)
  • api: update composite API spec (06eb2a6)
  • api: update composite API spec (10c56f8)
  • api: update composite API spec (e0335d9)
  • api: update composite API spec (1cf726b)
  • api: update composite API spec (9889b9c)
  • api: update composite API spec (f5bb242)
  • api: update composite API spec (21d2e59)
  • api: update composite API spec (7f579af)
  • api: update composite API spec (2edb41d)
  • api: update composite API spec (9f0c410)
  • api: update composite API spec (3836b7d)
  • api: update composite API spec (e428a7a)
  • api: update composite API spec (7476108)
  • api: update composite API spec (36ca7ff)
  • api: update composite API spec (c6223b6)
  • api: update composite API spec (7e91dae)
  • api: update composite API spec (826266e)
  • api: update composite API spec (cd0aa66)

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

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

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

- name: Install Rye
run: |
curl -sSf https://rye.astral.sh/get | bash
echo "$HOME/.rye/shims" >> $GITHUB_PATH
env:
RYE_VERSION: '0.44.0'
RYE_INSTALL_OPTION: '--yes'
- name: Install dependencies
run: |
rye sync --all-features
- name: Detect removed symbols
run: |
rye run python scripts/detect-breaking-changes.py "${{ github.event.pull_request.base.sha }}"

- 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 }} No newline at end of file

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 months ago

To fix this issue, we should explicitly set minimal required permissions for the workflow/job by adding a permissions block. The simplest and safest starting point is to set contents: read at the workflow level, as the steps only clone/checkout code and do not perform any write operations on issues, deployments, etc. This should be placed at the top level of the YAML file (directly below the name: or on: block) so all jobs inherit these permissions, unless overridden. No additional functionality is added or changed; this only restricts the escalated permissions that the workflow's GitHub token might inherit.


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
@@ -1,3 +1,5 @@
+permissions:
+  contents: read
 name: CI
 on:
   pull_request:
EOF
@@ -1,3 +1,5 @@
permissions:
contents: read
name: CI
on:
pull_request:
Copilot is powered by AI and may make mistakes. Always verify output.
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch 28 times, most recently from 614af0d to 80f56db Compare August 26, 2025 11:28
…ess.yml

* fix: add proper terraform annotations to connectivity_directory_service

* feat: add connectivity directory service APIs to openapi.stainless.yml
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch 2 times, most recently from 66b8c6a to 8ddeb81 Compare October 14, 2025 19:30
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 8ddeb81 to cb91b8d Compare October 14, 2025 20:03
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from cb91b8d to 7951fe3 Compare October 14, 2025 20:31
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch 2 times, most recently from 3befc94 to 57424e8 Compare October 14, 2025 21:10
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 57424e8 to bb87eb6 Compare October 14, 2025 21:40
* chore(abuse): rename path parameter
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from bb87eb6 to e3eb7f9 Compare October 15, 2025 16:43
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from e3eb7f9 to 6f09736 Compare October 21, 2025 01:39
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 6f09736 to 242e0c4 Compare October 21, 2025 20:03
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 242e0c4 to 7cba36c Compare October 22, 2025 15:22
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 7cba36c to e152888 Compare October 22, 2025 15:42
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from e152888 to c999123 Compare October 22, 2025 19:51
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from c999123 to 000f891 Compare October 22, 2025 19:54
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.

0 participants