Repository navigation
feat(sdk): record-deconsolidation and is_former from robosystems group-lifecycle Phase 3 - #280
Merged
Merged
Conversation
…p-lifecycle Phase 3 Regenerated from the local API on robosystems feature/group-lifecycle-phase-3: the record-deconsolidation operation with its request and response models, is_former on the ledger entity response, and the GraphQL schema with isFormer. Also sweeps premium_transferred on the ownership change response, which 2.31.0 missed. Claude-Session: https://claude.ai/code/session_015PxYaVzrbraKFeRALM7rXp
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
Regenerated from robosystems
feature/group-lifecycle-phase-3(group-lifecycle Phase 3, rs #1926): therecord-deconsolidationoperation with its request and response models, andis_formeron the ledger entity response. A client minor: additive only, generated tier.Waits on the robosystems release that carries rs #1926 before the new operation answers in production; the field and the operation resolve against any server once that release is deployed.
Also swept in by the regen:
premium_transferredon the ownership-change response (added by robosystems #1925, missed by 2.31.0), andisFormerin the checked-inschema.graphql(the hermetic ariadne-codegen gate is clean).Test plan
openapi.json+ the GraphQL schema)🤖 Generated with Claude Code
https://claude.ai/code/session_015PxYaVzrbraKFeRALM7rXp