feat: update to open api version 235.20.1 - #333
Merged
Conversation
szuperaz
approved these changes
Aug 18, 2026
oliverlaz
pushed a commit
that referenced
this pull request
Aug 18, 2026
🤖 I have created a release *beep* *boop* --- ## [0.8.1](v0.8.0...v0.8.1) (2026-08-18) ### Features * update to open api version 235.20.1 ([#333](#333)) ([d212346](d212346)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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
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 client from the
chatserverside spec at v235.20.1 (previously v235.16.3, #328). Generated from thechatworking tree atv235.20.1-91-g6c6373e6cd, so it also picks up spec changes merged after that tag.Chat: pinned messages
ChatApi.getPinnedMessages—GET /chat/channels/{type}/{id}/pinned_messages, with both id andpinned_atcursor pagination (id_gt/id_gte/id_lt/id_lte/id_around,pinned_at_after/pinned_at_after_or_equal/pinned_at_before/pinned_at_before_or_equal/pinned_at_around), pluslimit,offset,sort,member_custom_includeanduser_id.Channel.getPinnedMessagesconvenience wrapper onChannelApi.GetPinnedMessagesResponse(messages: MessageResponse[]).Chat: predefined filters
Named, server-stored filters for
QueryChannels:ChatApi.createPredefinedFilter—POST /chat/predefined_filtersChatApi.getPredefinedFilters—GET /chat/predefined_filters(optionalinclude_stats,sort)ChatApi.getPredefinedFilter/updatePredefinedFilter/deletePredefinedFilter—GET|PUT|DELETE /chat/predefined_filters/{name}Models:
CreatePredefinedFilterRequest,CreatePredefinedFilterResponse,UpdatePredefinedFilterRequest,UpdatePredefinedFilterResponse,GetPredefinedFilterResponse,QueryPredefinedFiltersResponse,PredefinedFilterResponse,PredefinedFilterStatsResponse(calls,max_latency_ms,last_seen),PerformanceAnalysisResponse(index/scan analysis withscore,recommendations,unindexed_fields,unindexed_sort_fields,warnings),SortParam.Permissions: custom permission CRUD
CommonApi.createPermission—POST /permissionsCommonApi.updatePermission—PUT /permissions/{id}CommonApi.deletePermission—DELETE /permissions/{id}Model:
PermissionRequest(action,name,description,owner,same_team,condition).getPermissionandlistPermissionsalready existed.Other additions
getOrCreateChannel(ChatApiandChannelApi) acceptsuser_id.QueryTeamUsageStatsRequest.team— filter results to a single team ID; empty string selects users not assigned to any team; mutually exclusive withnext.ModerationPayload.other_mediaandModerationPayloadResponse.other_media— media URLs from attachments outside the typed image/video/audio lists (custom attachment types such as GIF pickers).Documentation-only spec changes
restoreaction is now documented as state-aware: it reverses whichever of a delete, a block, or a shadow block currently applies (including both at once).unblockis marked deprecated in favour of it.push_typesis clarified as an allowlist — empty or omitted means no types trigger push.Codegen churn (no behaviour change)
Most of the diff is the generator's output style changing:
T[]→Array<T>in model and request typesdecoders.X→decoders['X']Record<string, any>→{ [key: string]: any }in decoder signaturesNormalizing those three patterns away shrinks the diff from ~4,450 changed lines to ~500, all accounted for above.
FeedsApiandModerationApihave no semantic change at all;VideoApionly reflows one call.None. No endpoints, models, or fields were removed, no signatures changed, and no optionality changed.
Verification
yarn lint— cleanyarn build— succeeds (vite bundles +tsc --emitDeclarationOnly)