Repository navigation
Conversation
This branch has not been deployed
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.
Regeneration previously updated a separate reference client while the supported SDK kept handwritten wire fields. The supported History, profile and webhook readers now consume schema-derived fields and request metadata.
The typed boundary retains the original JSON values for existing normalization. Checks detect incompatible consumed fields, unsupported required parameters, changed parameter locations and HTTP methods, and webhook envelope changes. The standalone reference transport remains separate.
Validation passed: 590 tests on Python 3.9/3.12, 38 incompatible schema mutations, strict mypy/lint, fresh installed wheel including sync/async calls. Generation freshness, packaged synthetic API calls and independent source review passed. The bundled API description and package version are unchanged; publication is a separate step.