release: 5.0.0 #2672
Open
release: 5.0.0 #2672
Conversation
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
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
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
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI 3 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
| @@ -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
bot
force-pushed
the
release-please--branches--main--changes--next
branch
28 times, most recently
from
614af0d to
80f56db
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
8192067 to
97818af
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
97818af to
3f36b98
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
3f36b98 to
23607d9
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
23607d9 to
a018936
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
a018936 to
8f6f9a4
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
8f6f9a4 to
3ea61a6
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
3ea61a6 to
4f8edbb
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
4f8edbb to
20dce21
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
20dce21 to
da1c110
Compare
* fix: tabbing on realtime-kit api resources
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
da1c110 to
da9c17f
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
da9c17f to
3276e02
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Automated Release PR
5.0.0 (2025-11-07)
Full Changelog: v4.3.1...v5.0.0
Features
Chores
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