Repository navigation
v0.7.0
Minor Changes
-
#12
4c2ee4dThanks @fernandoc00! - Add purchase scanner resources and extraction/review types from the backend contract. Support batch uploads, source downloads, versioned review and draft conversion, duplicate resolution, archive/restore, and inbound email history. Preserve structured batch failures and request options across pagination.Fix the default request-version header to the supported stable version
2026-06-01; the previous export-date pin was rejected by the backend. -
#12
396bf15Thanks @fernandoc00! - Re-pinspec/openapi.jsonfrom the current backend contract (399 paths / 483 operations) and regeneratesrc/generated/andsrc/resources/.BREAKING: the backend retired the legacy
clients/suppliersroutes (replaced bycontacts, which already covers the same identities and roles).ClientsResource,SuppliersResource, thefactuarea.clients/factuarea.suppliersclient properties and theSuppliertype export are removed; the SDK stays in0.x(breaking changes may land in a minor while pre-GA,docs/VERSIONING.md), so this is aminor, not amajor, release. Usecontactsfor every identity, role and profile operation.Harden
scripts/build-resources.mjs(design D4): operations withoutx-speakeasy-groupnow fail the generator with a listing ofmethod path operationIdbefore any output is written, instead of being silently dropped. The script also accepts--spec <path>/--out <dir>for testing against fixture specs.Add spec-guided
Idempotency-Keysupport (design D6):_send/_deleteinsrc/core/resource.tsaccept an optional fifth{ idempotent?: boolean }argument, and the generator sets it for non-POSTmutations the spec marks as requiring the header.src/core/http-client.ts'sMETHODS_WITH_IDEMPOTENCYalready generates the header unconditionally for everyPOST/PUT/PATCH/DELETE(a broader policy than D6, already shipped on this branch before this change) — that blanket behavior is kept as-is per the repo owner's instruction, so this is additive, not a narrowing.Method names follow
backend/docs/api/sdk-method-naming.md @ 1.1.0(up from the1.0.0cited by the generator before this change; the naming rule itself did not change).