Skip to content

feat: regenerate SDK from latest chat OpenAPI spec#269

Merged
mogita merged 1 commit into
mainfrom
feat/regenerate-from-chat-oas
Jun 22, 2026
Merged

feat: regenerate SDK from latest chat OpenAPI spec#269
mogita merged 1 commit into
mainfrom
feat/regenerate-from-chat-oas

Conversation

@mogita

@mogita mogita commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Regenerates the chat, common, feeds, moderation, and video clients and their models from the current chat OpenAPI spec.

Versioning

Titled feat: so the auto-release cuts a minor: latest tag v3.4.0 -> v3.5.0, matching the version = "3.5.0" already in pyproject.toml. This is the same changeset already shipped in getstream-php v7.4.0, so a minor bump matches precedent.

Added

  • New endpoints: moderation.analyze, .bulk_action_appeals, .get_setup_session, .upsert_setup_session; feeds.get_or_create_follow, .get_or_create_unfollow, .get_user_interests; chat.create_segment, .update_segment, .add_segment_targets; common.cancel_import_v2_task; video.report_client_call_event, plus the request/response models backing them.
  • New webhook events moderation.image_analysis.complete and moderation.text_analysis.complete.

Changed (compatibility note)

  • FlagResponse now represents the full flag record (created_at, target_message, target_user, reason, details, custom, etc.). The moderation flag-action acknowledgement, carrying item_id and duration, moved to the new FlagItemResponse, which moderation.flag() now returns. This resolves an upstream OpenAPI name collision where the acknowledgement was shadowing the rich record. The /api/v2/moderation/flag wire response is unchanged, so code reading item_id/duration off the parsed response is unaffected; only code referencing the FlagResponse type for those fields needs to switch to FlagItemResponse.
  • ChannelInput.config_overrides / ChannelDataUpdate.config_overrides are now typed as ChannelConfigOverrides instead of ChannelConfig.
  • enabled on DeliveryReceiptsResponse, ReadReceiptsResponse, TypingIndicatorsResponse is now a required bool (was Optional[bool]).
  • LLMRule.description, TargetResolution.bitrate, TranslationSettings.languages / .enabled are now optional.

Verification

  • models import clean; getstream/tests/test_webhook.py: 282 passed (covers the 2 new events).
  • ruff check + ruff format --check on regenerated files: clean.
  • AST diff old-vs-new confirms no classes removed (42 added) and no client method signatures removed or changed.

Regenerate the chat, common, feeds, moderation, and video clients and their
models from the current chat OpenAPI spec.

New endpoints: moderation.analyze, .bulk_action_appeals, .get_setup_session,
.upsert_setup_session; feeds.get_or_create_follow, .get_or_create_unfollow,
.get_user_interests; chat.create_segment, .update_segment, .add_segment_targets;
common.cancel_import_v2_task; video.report_client_call_event. Plus the new
moderation.image_analysis.complete and moderation.text_analysis.complete
webhook events.

Resolves an upstream OpenAPI name collision: FlagResponse now maps to the full
flag record, and the moderation flag-action acknowledgement (item_id, duration)
moves to the new FlagItemResponse, which moderation.flag() now returns. The
/api/v2/moderation/flag wire response is unchanged. Matches the same changeset
already shipped in getstream-php v7.4.0; released as a minor bump.
@coderabbitai

coderabbitai Bot commented Jun 22, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@mogita, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 45 minutes and 41 seconds. 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 @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 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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 746ecb69-9941-4da3-babb-dd8fe8695ed5

📥 Commits

Reviewing files that changed from the base of the PR and between 97c27cc and 5908b23.

📒 Files selected for processing (14)
  • CHANGELOG.md
  • getstream/chat/async_rest_client.py
  • getstream/chat/rest_client.py
  • getstream/common/async_rest_client.py
  • getstream/common/rest_client.py
  • getstream/feeds/feeds.py
  • getstream/feeds/rest_client.py
  • getstream/models/__init__.py
  • getstream/moderation/async_rest_client.py
  • getstream/moderation/rest_client.py
  • getstream/tests/test_webhook.py
  • getstream/video/async_rest_client.py
  • getstream/video/rest_client.py
  • getstream/webhook.py
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/regenerate-from-chat-oas

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@mogita mogita merged commit f552d7e into main Jun 22, 2026
39 of 40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant