Repository navigation
Publish corrected SDK authentication documentation in 26.10.1 - #9
Merged
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
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.
Publish the corrected Python authentication guide in the 26.10.1 SDK package metadata. The guide shows the explicit Authorization header used by the generated client and explains why
Configuration.access_tokenalone does not send it. Keep the previously corrected raw aiohttp streaming example.Align server/client version metadata, runtime version headers, embedded API version and current installation links at 26.10.1. All changes relative to the current main branch are exact version replacements; APIs, DTOs, dependency pins and SQL boundaries remain unchanged. Existing 26.10.0 assets and its tag are preserved.
The built wheel contains the corrected bearer and SSE instructions. The SDK's mandatory checks pass: 18 tests, lint/format and mypy across 144 files. The bearer recipe was checked over a real TCP socket using the published 26.10.0 runtime. The previous release's service, native PostgreSQL/DuckDB and installed-artifact qualification remains applicable to the unchanged implementation; PR CI validates this exact metadata source before publication.