feat: regenerate SDK from latest chat OpenAPI spec#65
Merged
Conversation
Regenerate the chat, common, feeds, moderation, and video clients and their models from the current chat OpenAPI spec. The release workflow derives the minor bump from this PR's feat: title and writes version.rb on merge, so the version file is intentionally left untouched here. 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 model, 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, so released as a minor bump.
mogita
force-pushed
the
feat/regenerate-from-chat-oas
branch
from
0604a22 to
df85e7a
Compare
mogita
added a commit
that referenced
this pull request
Jun 22, 2026
* fix: derive release bump only from the title bang marker The release workflow scanned the PR title and body for the substring "BREAKING CHANGE" and forced a major bump on any match. Prose that merely mentioned the phrase, including a sentence stating there was no breaking change, tripped it: PR #65 was intended as a minor (7.2.0) but cut 8.0.0. Treat the `!` marker in the conventional-commits title (e.g. `feat!:`) as the sole breaking-change signal and stop reading the PR body entirely. Drop the now-unused --body / --body-file options and the body plumbing in release.yml. * docs: align README release rules with title-only bump The Release Process section claimed a "BREAKING CHANGE" mention in the PR body/title forces a major bump. The workflow now derives the bump from the title's `!` marker only and ignores the body. Update the rules accordingly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Regenerates the chat, common, feeds, moderation, and video clients and their models from the current chat OpenAPI spec.
Versioning
version.rbis intentionally left at7.1.1. The release workflow derives the bump from this PR'sfeat:title (noBREAKING CHANGEmarker) and writesversion.rb+ tagsv7.2.0automatically on merge. This is the same changeset already shipped ingetstream-phpv7.4.0, so a minor bump matches precedent.Added
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.moderation.image_analysis.completeandmoderation.text_analysis.complete.Changed (compatibility note)
Models::FlagResponsenow represents the full flag record (created_at,target_message,target_user,reason,details,custom, etc.). The moderation flag-action acknowledgement, carryingitem_idandduration, moved to the newModels::FlagItemResponse, whichModeration#flagnow returns. This resolves an upstream OpenAPI name collision where the acknowledgement was shadowing the rich record. The/api/v2/moderation/flagwire response is unchanged, so code readingitem_id/durationoff the parsed response is unaffected; only code referencing theFlagResponsemodel class for those fields needs to switch toFlagItemResponse.ChannelInput#config_overridesandChannelDataUpdate#config_overridesare now typed asChannelConfigOverridesinstead of the fullChannelConfig.LLMRule#descriptionandTargetResolution#bitrateare now optional.Tests
make test: 283 examples, 0 failures.make lint(rubocop): 39 files, no offenses.