feat(client): regenerate for subgraph size_bytes and storage item types - #173
Merged
Merged
Conversation
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
Regeneration picking up two API changes: the byte-precision subgraph size fields already merged on the API's
main, and the storage-item documentation from RoboFinSystems/robosystems#1079 (transient/orphanitem types, enforcement semantics forusage_percentage). Generated against the local stack at #1079's tip; if that PR changes in review, this regen will be refreshed.Changes
models/only — noapi/or facade changes; sync and async paths unaffected.SubgraphResponse,SubgraphSummary: new optionalsize_bytes;ListSubgraphsResponse: new optionaltotal_size_bytes.size_mbremains, documented as derived.StorageItem,InstanceUsage: docstring updates only — the newtransient(blue-green build artifact) andorphan(unregistered leftover) item type values, and a note thatusage_percentagederives from durable bytes.typewas and remains a plainstr, so the new values are shape-compatible.Compatibility
ADDITIVE. All new fields are optional (
| None | Unset = UNSET); no removals, renames, signature changes, or requiredness flips — verified by reading the full emitted diff, not assumed from the regeneration. Rides the next minor.Testing
just test-allrun this session: 519 passed, 17 skipped; ruff format, lint, and basedpyright clean. No packaging changes, sojust build-packagewas not needed.