chore: release v0.106.0

[mabry1985]

Automated version bump to v0.106.0. Review + merge through the normal CI/review gate, then push the tag to cut the release: git checkout main && git pull && git tag -a v0.106.0 -m 'Release v0.106.0' && git push origin v0.106.0. The tag push triggers release.yml (Docker tags + GitHub Release + Discord) — don't also workflow_dispatch release.yml afterward (redundant; 422s on the duplicate).

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 45 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 3919001c-ece8-4a93-a45a-ae813e7ba253

📥 Commits

Reviewing files that changed from the base of the PR and between 6b80d7b and 1963703.

⛔ Files ignored due to path filters (2)

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

📒 Files selected for processing (2)

• pyproject.toml
• sites/marketing/data/changelog.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch prepare-release/v0.106.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[protoreview]

QA panel review — PASS

code-review-structural · head 19637031a75f · formal

[review-synthesizer completed: workflow code-review-structural:report]

The overall risk of this change is low, as the structural analysis pass flagged several dependency issues that were subsequently refuted by the verifier. No correctness or security defects were identified. The primary point of disagreement was the current state of PyPI versioning for LangChain, which the verifier resolved in favor of the PR's constraints. Verification resulted in the removal of all reported findings.

Gaps: The structural pass was performed but all its findings were refuted.

[]