release: 0.8.0

[stainless-app]

Automated Release PR

0.8.0 (2026-07-31)

Full Changelog: v0.7.0...v0.8.0

Features

• api: align reply extraction contracts (ef1ae2b)

---

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 of x-twitter-scraper

Bumps the package version from 0.7.0 to 0.8.0 across pyproject.toml, _version.py, and .release-please-manifest.json. The changelog notes new features including API changes for reply extraction, rich response contracts, and typed account outcomes.

^{Macroscope summarized 6d73565.}

[coderabbitai]

Warning

Review limit reached

@kriptoburak, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 10 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: a79e1cad-bc67-490a-a2a4-a406eed36664

📥 Commits

Reviewing files that changed from the base of the PR and between 23ab238 and 6d73565.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (4)

• .release-please-manifest.json
• CHANGELOG.md
• pyproject.toml
• src/x_twitter_scraper/_version.py

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Fix failing CI checks

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-please--branches--main--changes--next

---

_{Comment @coderabbitai help to get the list of available commands.}

[furkanerday]

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]

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.

[stainless-app]

🤖 Release is at https://github.com/Xquik-dev/x-twitter-scraper-python/releases/tag/v0.8.0 🌻