chore(release): 0.4.31.1 — Slack #138 + #95 fixes#177
Conversation
Python-only patch on 4.31.0 (UPSTREAM_PARITY unchanged). - Slack #138: empty-DM thread_ts fetch routes to conversations.history (PR #175) - Slack #95: thread team_id to chat.startStream for Enterprise Grid (PR #176) - docs: mark Linear agent-sessions mode experimental (unverified vs live tenant, #151) - version 0.4.31 -> 0.4.31.1; CHANGELOG; CLAUDE.md mapping
|
Warning Review limit reached
More reviews will be available in 56 minutes and 1 second. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
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. Comment |
There was a problem hiding this comment.
Code Review
This pull request bumps the SDK version to 0.4.31.1, updating pyproject.toml, README.md, CLAUDE.md, and CHANGELOG.md. It documents Slack adapter bug fixes regarding empty-DM thread_ts fetch routing and Enterprise Grid team_id streaming, and adds a warning note in the Linear adapter configuration marking the 'agent-sessions' mode as experimental. There are no review comments, so no further feedback is provided.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Cuts 0.4.31.1 — a Python-only patch on
4.31.0(UPSTREAM_PARITYunchanged at4.31.0) bundling the two merged Slack adapter fixes.Included (already merged to main)
thread_tsfetch routes toconversations.historyinstead ofconversations.replies(ts=''); non-empty path byte-identical.chat.startStreamthreadsteam_id(=recipient_team_id) for Enterprise Grid; verified end-to-end againstslack_sdkthat it reaches the API call.This PR
pyprojectversion0.4.31→0.4.31.1; README status; CLAUDE.md version-mapping"agent-sessions"mode experimental inLinearAdapterConfig(schema-hardened but unverified vs a live tenant, Port Linear agent sessions (adapter-linear) — deferred from 0.4.30 #151)Validation (local)
ruff + format clean · audit 0 hard failures · pyrefly 0 · fidelity 732/732
--strict@ chat@4.31.0 · full suite green.Next: deploy to customer-demo (git-ref) and live-verify #138 (DM fetch) + #95 (Grid stream) before the PyPI publish.
🤖 Generated with Claude Code