Fix access_token description in revokeChannelToken - #1050
Merged
Conversation
mokuzon
approved these changes
Jul 28, 2026
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.
line/line-openapi#130
There was an openapi-generator bug (OpenAPITools/openapi-generator#24004, fixed in v7.24.0 via OpenAPITools/openapi-generator#24192).
It generated
revokeChannelToken'saccess_tokendoc asA short-lived or long-lived channel access token.instead of this spec'sChannel access token, and the SDKs merged it.With v7.24.0, regeneration now tries to revert it:
Since the current SDK wording is correct for this endpoint (
POST /v2/oauth/revokeonly accepts short-lived or long-lived tokens), this PR updates the spec to match it instead.The regeneration diff disappears and the PRs above stay closed.