Repository navigation
Align History ids and generated API client - #18
Merged
Merged
Conversation
KonstantinSerebryakov
approved these changes
Oct 30, 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
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.
Align user-list filtering with the current public History API: send one ids value and reject repeated ids before HTTP. Bands, risk signals, source and campaign remain repeatable.
Refresh generated clients from OpenAPI #41, including removal of unsupported relation parameters. 600 Python tests, Ruff and mypy passed locally. Request-shape regression tests cover encoded User HID and rejection before HTTP. CI must pass before merge.
This PR updates source and generated types; it does not create a registry release.