release: 0.8.0 - #31
Conversation
|
Warning Review limit reached
Next review available in: 58 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (49)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
furkanerday
left a comment
furkanerday
left a comment
There was a problem hiding this comment.
Blocking reproducibility issue: bumps the project to 0.7.1, but the release PR does not update . The required job already fails because reports that the lockfile needs to be updated, and also fails. Regenerate and commit the lockfile for this version bump, then rerun all required checks.
furkanerday
left a comment
furkanerday
left a comment
There was a problem hiding this comment.
Blocking reproducibility issue at pyproject.toml:3: the project version is bumped to 0.7.1, but the release PR does not update uv.lock. The required Fuzz Query Strings job fails because uv export --locked reports that the lockfile needs to be updated, and Tests & Coverage also fails. Regenerate and commit uv.lock for this version bump, then rerun all required checks.
Regenerate every SDK from the exact production OpenAPI contract.
0e47ac2 to
6e6fa54
Compare
6e6fa54 to
611a60a
Compare
1 participant
Automated Release PR
0.8.0 (2026-07-31)
Full Changelog: v0.7.0...v0.8.0
Features
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
Note
Release version 0.8.0 with expanded tweet and account response models
accounts.createnow returnsAccountCreateResponse(a union ofSanitizedXAccount,XAccountConnectionAttemptPending, andXAccountConnectionChallenge) instead of a genericobjecttweets.get_repliesnow acceptslimitandmodeparameters and returnsTweetGetRepliesResponseinstead ofPaginatedTweetsEmbeddedTweet,SearchTweet, andTweetDetailgain many optional fields:article,card,community_note,edit,note_tweet,place,previous_counts,view_state, and recursivequoted_tweet/retweeted_tweetvia forward referencesTweetMediagains extended metadata fields (alt text, aspect ratio, crop rects, sizes, dimensions);UserProfileadds affiliation, highlights, and identity verification fields while removingcan_dm,viewer_followed_by, andviewer_followingupdate_forward_refs()/model_rebuild()in types/init.pyUserProfile.can_dm,UserProfile.viewer_followed_by,UserProfile.viewer_following, andCommunity.is_member/roleare removed, which is a breaking change for consumers relying on those fieldsMacroscope summarized 611a60a.