release: 0.6.1

[stainless-app]

Automated Release PR

0.6.1 (2026-07-30)

Full Changelog: v0.6.0...v0.6.1

---

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

---

Summary by cubic

Release 0.6.1 of x-twitter-scraper. Bumps version in code and docs; updates CHANGELOG; no functional changes.

• Migration
  • Update your Gemfile to gem "x-twitter-scraper", "~> 0.6.1" and run bundle update x-twitter-scraper.

^{Written for commit 1f8bafb. Summary will update on new commits.}

Note

Release version 0.6.1 of the x_twitter_scraper gem

Bumps XTwitterScraper::VERSION to 0.6.1 and updates the install snippet in README.md to reference ~> 0.6.1. Also updates CHANGELOG.md and the release manifest.

^{Macroscope summarized 1f8bafb.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	x-twitter-scraper@​0.6.0 ⏵ 0.6.1	N/A	N/A	N/A	N/A	N/A

View full report

[coderabbitai]

Warning

Review limit reached

@stainless-app[bot], you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 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: d01f5ed6-80b3-4d77-952a-173e7abdbbec

📥 Commits

Reviewing files that changed from the base of the PR and between 187451d and 1f8bafb.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (4)

• .release-please-manifest.json
• CHANGELOG.md
• README.md
• lib/x_twitter_scraper/version.rb

---

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

[furkanerday]

Reviewed the complete release diff, description, commit history, checks, discussion, repository policy, version metadata, changelog, lockfile, dependency and release integrity, licensing, DCO applicability, and reproducibility. The version updates are consistent, all required checks are green, and no actionable review threads remain.

[stainless-app]

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