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 4 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
e3653cc to
6bfc71b
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
6bfc71b to
060d00f
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
060d00f to
30c8b89
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
30c8b89 to
d4f7c1e
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
d4f7c1e to
9e58335
Compare
…Catalog routes * feat(r2_data_catalog): Configure SDKs/Terraform to use R2 Data Catalog routes
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
9e58335 to
1a0412a
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
1a0412a to
d8a95b0
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
d8a95b0 to
58c1af9
Compare
* chore(zero_trust_gateway_proxy_endpoint): unsupported auth scheme * chore(abuse_report): unsupported auth scheme
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
58c1af9 to
6e47727
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
6e47727 to
6d5ca7b
Compare
* docs: Deprecate API Shield Schema Validation resources This change marks old schema validation resources as deprecated.
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
6d5ca7b to
1643c4b
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
1643c4b to
b5b787a
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
b5b787a to
ae450fc
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-12-08)
Full Changelog: v4.3.1...v5.0.0
Features
Bug Fixes
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