release: 2.3.0-rc1 - #242
Conversation
![hackerone-code[bot]](https://avatars.githubusercontent.com/in/3434?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ This pull request was succesfully scanned and it was determined that it does not contain any changes that present immediate security concerns. If you would still like for it to be reviewed by an expert from our reviewer community, you can submit it manually via the HackerOne PullRequest dashboard.
⏱️ Latest scan covered changes up to commit 0351f6f (latest)
0351f6f to
a780648
Compare
There was a problem hiding this comment.
✅ This pull request was succesfully scanned and it was determined that it does not contain any changes that present immediate security concerns. If you would still like for it to be reviewed by an expert from our reviewer community, you can submit it manually via the HackerOne PullRequest dashboard.
⏱️ Latest scan covered changes up to commit 856498e (latest)
856498e to
d1f5948
Compare
There was a problem hiding this comment.
✅ This pull request was succesfully scanned and it was determined that it does not contain any changes that present immediate security concerns. If you would still like for it to be reviewed by an expert from our reviewer community, you can submit it manually via the HackerOne PullRequest dashboard.
⏱️ Latest scan covered changes up to commit 61bbe3f (latest)
61bbe3f to
1c5e20c
Compare
There was a problem hiding this comment.
✅ This pull request was succesfully scanned and it was determined that it does not contain any changes that present immediate security concerns. If you would still like for it to be reviewed by an expert from our reviewer community, you can submit it manually via the HackerOne PullRequest dashboard.
⏱️ Latest scan covered changes up to commit 466e02a (latest)
466e02a to
aa0d06d
Compare
7cb49c1 to
aa0d06d
Compare
There was a problem hiding this comment.
🔍 This pull request has been sent to HackerOne's PullRequest review team because our automation detected one or more changes with potential security impact or requires further evaluation. Experts are now being assigned to this review based on relevant expertise and will validate or dismiss any security findings accordingly and post their feedback as comments within this pull request.
⏱️ Latest scan covered changes up to commit 74daebe (latest)
Check the status or cancel this secure code review here.
There was a problem hiding this comment.
✅ Jacob reviewed all the included code changes and associated automation findings and determined that there were no immediately actionable security flaws. Note that they will continue to be notified of any new commits or comments and follow up as needed throughout the duration of this pull request's lifecycle.
Reviewed with ❤️ by PullRequest
74daebe to
851522b
Compare
194ca08 to
cdbd4b3
Compare
5427d0a to
279d7df
Compare
ba23b1f to
3e86693
Compare
3e86693 to
3b385f3
Compare
3b385f3 to
d1338bb
Compare
d1338bb to
b90b935
Compare
b90b935 to
7bd8608
Compare
7bd8608 to
56af105
Compare
Release version edited manuallyThe Pull Request version has been manually set to If you instead want to use the version number |
56af105 to
2552ca4
Compare
|
🤖 Release is at https://github.com/writer/writer-python/releases/tag/v2.3.0-rc1 🌻 |
stainless-app
Bot
added
autorelease: pre-release
autorelease: tagged
and removed
autorelease: pending
labels
1 participant
Automated Release PR
2.3.0-rc1 (2025-08-12)
Full Changelog: v2.2.1...v2.3.0-rc1
Features
Bug Fixes
Chores
Documentation
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