chore: adopt hotdata 0.5.0 SDK#30
Merged
Merged
Conversation
Bump the hotdata dependency floor from >=0.4.1 to >=0.5.0. The 0.5.0 release is backward compatible for everything the framework uses; the only API changes are additive (optional 'format' field on LoadManagedTableRequest and optional 'format' param on ResultsApi.get_result), so no framework code changes were required.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
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
Bump the
hotdatadependency floor from>=0.4.1to>=0.5.0.The 0.5.0 release is backward compatible for everything the framework uses. The only API changes are additive:
formatfield onLoadManagedTableRequestformatparameter onResultsApi.get_resultSo no framework code changes were required.
Verification
pytest— 54 passedruff check— cleanmypy— identical error count (zero diff) vs 0.4.1uv lock --check— consistent