chore(sdk): regenerate from API 1.8.3 — passkey re-auth proof fields - #188
Merged
Conversation
Passkey enrollment re-auth proof fields (password/assertion on PasskeyRegisterOptionsRequest), register endpoints drop their API-key security entry, advisory file_size_bytes on FileUploadRequest, and the truthful checkout-status operation_id description. Additive only.
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
Regeneration against the merged API (robosystems#1164, #1165, #1161, #1163 — spec 1.8.3). Strictly additive: client minor. Mirror of typescript-client#195.
Changes
PasskeyRegisterOptionsRequestgains optionalpassword/assertion(settings-lane re-auth proof; forced lane unchanged); the two register endpoints drop their API-key security entry.FileUploadRequest.file_size_bytes— optional advisory pre-check (robosystems#1161).CheckoutStatusResponse.operation_iddescription states it is always null for webhook-driven provisioning (robosystems#1163).GraphQL SDL snapshot already current — no drift, hermetic gate untouched. None of this touches the stable tier (integration-template emit symbols unaffected).
Breaking Changes
None — additive fields and description updates only.
Testing
just test-allgreen — 526 passed, 17 skipped; ruff, format, basedpyright clean.