feat(client): regenerate for graph-scoped API keys - #170
Merged
Conversation
…d extension Additive: graph_id on APIKeyInfo and CreateAPIKeyRequest (graph-scoped keys, robosystems#1064); download_extension on BackupResponse and the updated backup download docstring.
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.
Summary
Client regeneration against the updated OpenAPI spec. Additive only — rides a minor under the 1.x contract:
APIKeyInfo.graph_idandCreateAPIKeyRequest.graph_id— optional graph scope for API keys (pairs with robosystems#1064; merge that first)BackupResponse.download_extension+ updated backup-download docstring — catching up with the self-describing backup format already on mainTesting
just test-allgreen: 518 passed, lint + typecheck clean