Skip to content

chore(spec): sync upstream specs 2026-11-02 (no model changes) - #566

Merged
TexasCoding merged 1 commit into
mainfrom
fix/565-spec-drift
Nov 2, 2026
Merged

TexasCoding merged 1 commit into
mainfrom
fix/565-spec-drift

Conversation

@TexasCoding

Copy link
Copy Markdown
Owner

Closes #565

Re-vendored specs with scripts/sync_spec.py. The hashes match the issue. scripts/generate.py produced byte-identical kalshi/_generated/models.py.

What changed

  • core openapi 3.35.0: x-go-type: json.RawMessage added on LiveData/Milestone details and Market custom_strike. These are Go codegen hints only.
  • perps openapi: description-only changes saying exchange_index and the exchange shard fields are deprecated on Perps. Market.exchange_index is now marked deprecated: true. No fields were added, removed, renamed or changed in required status.

Blast radius (written by hand; GitNexus unavailable): only specs/openapi.yaml and specs/perps_openapi.yaml. No runtime code or models changed, so this has no user-facing impact and needs no release. A possible follow-up is a DeprecationWarning for perps exchange_index params, which upstream will remove later.

Gates: ruff OK, mypy OK (161 files), 5062 unit tests passed / 3 skipped, 930 strict contract tests passed.

@TexasCoding
TexasCoding merged commit 9e16316 into main Nov 2, 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.

Spec drift 2026-11-02: openapi 3.35.0 [content-changed] (paths 111→111, fp c10e35b5)

1 participant