Repository navigation
feat: support channel-owned dedicated integrations - #109
Merged
alick-liming merged 2 commits intoOct 27, 2026
Merged
Conversation
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.
Summary
Adds a
DedicatedIntegrationsservice for all eight channel-owned integration endpoints. Existing public integration methods keep their names and routes; bilingual usage guidance explains ownership, permissions, and which service to choose.Syncs only the integration-related OpenAPI contracts. Generated requests keep string constraints typed and preserve omitted settings versus an explicit empty replacement.
Known
plugin_typevalues can be used to create dedicated integrations directly. Type lookup is optional and requires Integrations Read permission.Validation
make: formatting, lint (0 issues), race tests, and build passed.