SDKs 0.25.0 read a response that leaves a field out
The Python SDK 0.25.0 reads a response that leaves out a documented field instead of raising, keeps working on pydantic 1, and declares a pydantic version that actually works. The TypeScript and Go SDKs only update one field description.
SDK
The TypeScript (@predictorsdk/client), Python (predictorsdk), and Go (github.com/PredictorSDK/sdk-go) SDKs are released at 0.25.0. Nothing in a request or response changed shape.
- Python reads a response that leaves a field out. A field the API documents as always present, but that a response leaves out (for example during an API rollback), now reads
Noneinstead of raisingParsingError. The TypeScript and Go SDKs already behaved this way. Dates and datetimes still come back asdateanddatetime, nested objects as SDK models, and unknown fields are kept. - Two small Python differences. A whole number in a decimal field stays a whole number (
price: 1reads1, not1.0). An error body that does not match the documented error shape raises the usual typed error for its status, withcodeset toNone, instead ofParsingError. - pydantic 1 still works, and the stated minimum is real. The package now requires
pydantic>=1.10.8. It said>=1.9.2, but on Python 3.9, pydantic 1.10.0 to 1.10.7 could not import the SDK at all, so pip could install a combination that failed on import. CI now tests the SDK on pydantic 1 as well as 2. See the Python SDK page. - TypeScript and Go. Only the description of the catalog's
snapshot.observed_atchanged. It now says the time marks when the oldest crawl started, as the API does since today.
We checked each published package against the production API before announcing it:
- Python 0.25.0 ran on Python 3.9 with pydantic 1.10.8 and on Python 3.12 with pydantic 2.14, and pip refuses pydantic 1.10.7 next to it.
- The TypeScript package loaded with
require()and withimport. - The Go module built.
Each listed a matched event, and Python read the event's start and the snapshot time as datetimes on both pydantic versions.