chore(deps): move to robosystems-client 2.0.0 - #18
Merged
Merged
Conversation
The API regrouped its RoboLedger operations from one OpenAPI tag into
eight workflow-stage tags. openapi-python-client names its module
directories after the tag, so the three emit operations moved packages:
api.extensions_robo_ledger.create_event_block
-> api.robo_ledger_ledger_events.create_event_block
api.extensions_robo_ledger.assert_metrics
-> api.robo_ledger_information_blocks.assert_metrics
api.extensions_robo_ledger.create_taxonomy_block
-> api.robo_ledger_taxonomy_mapping.create_taxonomy_block
Symbol names, signatures and request models are unchanged — only the
import path. No endpoint moved and no request shape changed; the
server's OpenAPI document differs only in `tags`.
Pin moves to >=2,<3 and the lockfile to 2.0.0.
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
Moves to
robosystems-client2.0.0. The API regrouped its RoboLedger operations from a single OpenAPI tag into eight workflow-stage tags (RoboFinSystems/robosystems#1451);openapi-python-clientnames its module directories after the tag, so the three operations this repo emits with moved packages.Changes
Import paths only — the symbols, their signatures and their request models are unchanged:
create_event_blockapi.extensions_robo_ledgerapi.robo_ledger_ledger_eventsassert_metricsapi.extensions_robo_ledgerapi.robo_ledger_information_blockscreate_taxonomy_blockapi.extensions_robo_ledgerapi.robo_ledger_taxonomy_mappingsrc/integration/emit/events.py— one importsrc/integration/emit/metrics.py— two importspyproject.toml— pin>=1,<2→>=2,<3;uv.lockfollows to 2.0.0No endpoint moved and no request or response shape changed: the server's OpenAPI document differs from the previous one only in
tags. The emit calls themselves are untouched.Testing
just test-all— tests, ruff format, ruff check and basedpyright all clean against the installed 2.0.0.🤖 Generated with Claude Code