chore(sdk): regenerate from API 1.9.x - #192
Merged
Merged
Conversation
First regeneration since 2026-08-13 (API 1.8.3), so this carries nine days of surface, not one change. Everything removed is named below. REMOVED (one model, one enum member in three places): - SECConnectionConfig, and the sec_config field on CreateConnectionRequest - SEC = "sec" from ConnectionProviderInfoProvider, CreateConnectionRequestProvider and ListConnectionsProviderType0 The SEC connection provider is gone from the API (robosystems #1248). It was a filing-driven entity-creation path predating the shared SEC repository, disabled in every deployed environment, and its sync had degenerated to a no-op reported as a pending operation. SEC filings still arrive nightly into the shared SEC repository; only the per-graph connection surface goes. Nothing else is removed anywhere in the diff. This is generated-tier surface under the two-tier contract, so it rides a minor. It also meets the dead-surface clause independently: it never functioned in a shipped configuration, its only consumer was the roboledger-app UI removed in roboledger-app #316, and the change is symbol resolution only. ADDED: - terminate_schedule, with TerminateScheduleRequest/Response and OperationEnvelopeTerminateScheduleResponse(+Status) - base_anchor on the forecast request models (CreateForecastRequestBaseAnchor, ForecastMechanicsBaseAnchor, UpdateForecastRequestBaseAnchorType0) - reauth_assertion on UpdateUserRequest - CloseReceipt and the closeReceipt field on the period in schema.graphql CHANGED, DESCRIPTIONS ONLY: - sync_connection now documents the split the API made real: QuickBooks returns a pending envelope carrying the run's task_id, while a push-based provider returns completed with a null task_id and nothing to poll - create_taxonomy_block and CreateTaxonomyBlockRequest reword one paragraph. This is stable-tier surface, so it is worth stating plainly that no signature or field moved - tier_capacity drops "scalable" from its status description; backup_response documents the 'final' backup taken at deprovision - get_connection_options, execute_sql, list_user_api_keys, update_user, get_graph_capacity and several roboledger models pick up the docs-hygiene pass Version left at 1.10.1 to bump at publish.
jfrench9
added a commit
to RoboFinSystems/robosystems-typescript-client
that referenced
this pull request
Aug 22, 2026
Companion to **RoboFinSystems/robosystems-python-client#192**. This carries accumulated API surface, not one change — everything removed is named below. ## Removed — one type, one union member in two places | Symbol | Where | |---|---| | `SecConnectionConfig` | deleted from `types.gen.ts` and root exports | | `sec_config` | field on the create-connection request | | `'sec'` | provider union on create-connection and list-connections | The SEC connection provider is gone from the API (**RoboFinSystems/robosystems#1248**). It was a filing-driven entity-creation path predating the shared SEC repository, disabled in every deployed environment (`CONNECTION_SEC_ENABLED=false` in both prod and staging SSM, since deleted), and its sync had degenerated to a no-op reported as a pending operation. SEC filings still arrive nightly into the shared SEC repository. Only the per-graph connection surface goes. **I diffed the full export symbol set** (both `export {}` and `export type {}` in `sdk/index.ts`): `SecConnectionConfig` is the only removal; everything else is additive. ## Why a minor, not a major `SecConnectionConfig` lives in the generated `/sdk` tree, which the two-tier contract explicitly places in the generated tier — moved on a client minor with each removal named. The facades (`LedgerClient`, `InvestorClient`, `LibraryClient`) never referenced it; I grepped `clients/` to confirm it appears nowhere outside `sdk/`. It also satisfies the dead-surface clause independently: it never functioned in a shipped configuration, its only consumer was the roboledger-app UI removed in **RoboFinSystems/roboledger-app#316**, and the change is symbol resolution only. ## Added - `terminateSchedule`, with `TerminateScheduleRequest`/`Response`(`2`), `TerminateScheduleData`/`Error`(`s`)/`Responses`, and `OperationEnvelopeTerminateScheduleResponse` - `CloseReceipt` in the generated GraphQL types (+44 lines) ## Changed — descriptions only - **`syncConnection`** documents the split the API made real: QuickBooks returns a `pending` envelope carrying the run's `task_id`; a push-based provider returns `completed` with a null `task_id` and nothing to poll. The prior text still described SEC downloading EDGAR filings in 5–10 minutes, which had not been true for some time. - `createConnection` and `getConnectionOptions` drop their SEC clauses. ## Validation `npm run test:all` green — prettier, eslint, `tsc --noEmit`, 10 test files / 302 tests, and a clean `tsc` build. Pre-commit re-ran the same gate. Version left at **1.10.1** for you to bump at publish.
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.
First regeneration since 2026-08-13 (API 1.8.3), so this carries nine days of surface, not one change. Everything removed is named below — no removal rides silently.
Removed — one model, one enum member in three places
SECConnectionConfigsec_configCreateConnectionRequestSEC = "sec"ConnectionProviderInfoProvider,CreateConnectionRequestProvider,ListConnectionsProviderType0The SEC connection provider is gone from the API (RoboFinSystems/robosystems#1248). It was a filing-driven entity-creation path predating the shared SEC repository, disabled in every deployed environment (
CONNECTION_SEC_ENABLED=falsein both prod and staging SSM, since deleted), and its sync had degenerated to a no-op reported as a pending operation.SEC filings still arrive nightly into the shared SEC repository. Only the per-graph connection surface goes.
I verified this is the only removal in the diff — a field/enum-level sweep across all 38 changed files returns nothing but the SEC symbols above.
Why a minor, not a major
SECConnectionConfigis generated-tier surface, which the two-tier contract moves on a client minor with each removal named in the release notes. It also satisfies the dead-surface clause independently: it never functioned in a shipped configuration, its only consumer was the roboledger-app UI removed in RoboFinSystems/roboledger-app#316, and the change is symbol resolution only.I checked the frozen stable-tier set by reading
robosystems-integration-template/src/integration/emit/*.pyrather than recalling it. None of what it imports is removed here.Added
terminate_schedule, withTerminateScheduleRequest/ResponseandOperationEnvelopeTerminateScheduleResponse(+Status)base_anchoron the forecast models —CreateForecastRequestBaseAnchor,ForecastMechanicsBaseAnchor,UpdateForecastRequestBaseAnchorType0reauth_assertiononUpdateUserRequestCloseReceiptand thecloseReceiptfield on the period inschema.graphql(+59 lines)Changed — descriptions only
sync_connectiondocuments the split the API made real: QuickBooks returns apendingenvelope carrying the run'stask_id; a push-based provider returnscompletedwith a nulltask_idand nothing to poll.create_taxonomy_block/CreateTaxonomyBlockRequestreword one paragraph. This is stable-tier surface, so worth stating plainly: no signature, field, or type moved — the diff is entirely docstring.tier_capacitydropsscalablefrom its status description (the field staysstr);backup_responsedocuments thefinalbackup taken at deprovision.get_connection_options,execute_sql,list_user_api_keys,update_user,get_graph_capacityand several roboledger models pick up the docs-hygiene pass from main.Validation
just test-allgreen — 526 passed / 17 skipped, ruff check, ruff format, basedpyright 0 errors 0 warnings. Pre-commit re-ran the same gate.Version left at 1.10.1 for you to bump at publish.