chore(deps): relock robosystems-client to 1.12.0 - #8
Merged
Merged
Conversation
Member
Author
|
@claude please review this PR |
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
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.
Summary
Relocks
robosystems-clientfrom 1.1.0 to 1.12.0 under the unchanged>=1,<2pin — the lock had not moved since the client's 1.0 line. 1.12.0 is generated from the API's 1.10 line; the demo's emit path (inherited from the integration template) resolves against it, which the typecheck demonstrates.Changes
uv.lock— the resolution only;pyproject.tomlis untouched.Run Impact
None on the provision → demo → teardown loop: the operations it calls are on the stable tier and unchanged. The reviewer tenant provisioned from this repo is unaffected.
Testing
just test-all— exit 0: 6 tests, ruff check and format clean, basedpyright 0 errors.