Skip to content

chore: regenerate _connect from current protos (was frozen at 07-22) - #18

Merged
rodnnnney merged 1 commit into
mainfrom
fix/regen-connect-latest-protos
Jul 28, 2026
Merged

chore: regenerate _connect from current protos (was frozen at 07-22)#18
rodnnnney merged 1 commit into
mainfrom
fix/regen-connect-latest-protos

Conversation

@rodnnnney

@rodnnnney rodnnnney commented Jul 28, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

The vendored Connect tree is produced by scripts/generate-connect.sh, which
runs by hand and is in no workflow, so it does not move when Speakeasy
regenerates. Nobody had run it since #13 on 07-22, and 1.0.6 shipped a fresh
REST surface bolted to a six-day-old streaming surface.

Regenerated against demo2 f1576e584f. All 13 public RPCs added since 07-22 are
now present (previously 0 of 13):

  GetAppServerStatus, RestartAppServer, ListPatchObjects, CompactChat,
  GetSandboxLeaseSettings, SetSandboxLeaseSettings, ListFavorites,
  GetAgentDBSchema, GetAgentDBTablePreview, GetAppDBSchema,
  GetAppDBTablePreview, UpdateMemberTheme, GetPlaybookBillingStats

Verified: pyright 0 errors, mypy clean across 1751 files, pylint 10.00/10,
and a live client exposes the new methods (note connect-python snake-cases
runs of capitals, so GetAgentDBSchema becomes get_agent_d_b_schema).

Worth fixing properly: nothing detects this drift. A publish can ship a
_connect tree of arbitrary age and no check complains. Either wire the script
into sdk_generation.yaml or add CI that fails when _connect is older than
demo2's protos.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@rodnnnney
rodnnnney merged commit 51ed2bd into main Jul 28, 2026
6 checks passed
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