Skip to content

chore(sdk): regenerate from API 1.9.x - #199

Merged
jfrench9 merged 1 commit into
mainfrom
chore/regenerate-sdk-sec-removal
Aug 22, 2026
Merged

chore(sdk): regenerate from API 1.9.x#199
jfrench9 merged 1 commit into
mainfrom
chore/regenerate-sdk-sec-removal

Conversation

@jfrench9

Copy link
Copy Markdown
Member

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.

First regeneration in some time, so this carries accumulated surface, not
one change. Everything removed is named below.

REMOVED (one type, one union member in two places):

- SecConnectionConfig, and the sec_config field on the create-connection
  request
- 'sec' from the provider union on create-connection and list-connections

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 in the diff.

This lives in the generated /sdk tree, which the two-tier contract puts
in the generated tier, so it rides a minor. The facades — LedgerClient,
InvestorClient, LibraryClient — never referenced it. 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:

- terminateSchedule, with TerminateScheduleRequest/Response(2),
  TerminateScheduleData/Error(s)/Responses and
  OperationEnvelopeTerminateScheduleResponse
- CloseReceipt in the generated GraphQL types

CHANGED, DESCRIPTIONS ONLY:

- syncConnection 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
- createConnection and getConnectionOptions drop their SEC clauses

Version left at 1.10.1 to bump at publish.
@jfrench9
jfrench9 merged commit bc8e0bd into main Aug 22, 2026
5 checks passed
@jfrench9
jfrench9 deleted the chore/regenerate-sdk-sec-removal branch August 22, 2026 02:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant