@curviate/sdk 0.21.0 → 0.23.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +52 -0
- package/dist/index.d.ts +371 -64
- package/package.json +1 -1
- package/src/generated/types.ts +371 -64
package/CHANGELOG.md
CHANGED
|
@@ -9,6 +9,58 @@ Versioning: semantic. Minor for additive changes, patch for bug fixes; no stabil
|
|
|
9
9
|
|
|
10
10
|
## [Unreleased]
|
|
11
11
|
|
|
12
|
+
## [0.23.0] - 2026-08-18
|
|
13
|
+
|
|
14
|
+
Regeneration against the deployed OpenAPI document following recent server
|
|
15
|
+
changes. Nothing was hand-edited.
|
|
16
|
+
|
|
17
|
+
**Minor, not patch: removing an optional field from a request-body type can
|
|
18
|
+
red a consumer's typecheck** (an object literal or a spread that still
|
|
19
|
+
supplies `network_distance` now fails structural typing), even though the
|
|
20
|
+
field never functioned against the server. That is a breaking change for a
|
|
21
|
+
0.x consumer, and under 0.x, minor is how it gets signalled.
|
|
22
|
+
|
|
23
|
+
### Changed
|
|
24
|
+
|
|
25
|
+
- **`SearchCompaniesBody` drops `network_distance`.** The field was removed
|
|
26
|
+
server-side; it never filtered anything, and declaring it invited a
|
|
27
|
+
request the server ignores. `SearchPeopleBody` is unaffected and keeps its
|
|
28
|
+
own `network_distance`.
|
|
29
|
+
- **`GET /v1/webhooks` cursor description now says it is decodable.** Previously
|
|
30
|
+
"Opaque pagination cursor from a previous response"; now describes it as
|
|
31
|
+
decodable and to be passed back verbatim. No type change.
|
|
32
|
+
|
|
33
|
+
## [0.22.0] - 2026-08-17
|
|
34
|
+
|
|
35
|
+
Regeneration against the deployed, served OpenAPI document at server commit
|
|
36
|
+
`7bdf0af7` (`https://api.curviate.com/.well-known/openapi.json`). Nothing was
|
|
37
|
+
hand-edited.
|
|
38
|
+
|
|
39
|
+
**Minor, not patch, because the section arrays gained declared item shapes.**
|
|
40
|
+
No method, path, or response was added or removed, nothing became required,
|
|
41
|
+
and every new field is optional on a type that still carries an open
|
|
42
|
+
`[key: string]: unknown` index signature, so reading code that compiled
|
|
43
|
+
against 0.21.0 continues to compile. Code that *constructs* one of these
|
|
44
|
+
objects with a field whose type conflicts with the declared one (a hand-rolled
|
|
45
|
+
test fixture, most likely) will now be rejected, which is the only way this
|
|
46
|
+
release can break a consumer.
|
|
47
|
+
|
|
48
|
+
### Changed
|
|
49
|
+
|
|
50
|
+
- **Recruiter and Sales Navigator profile section arrays now declare their item
|
|
51
|
+
shape.** `skills`, `experience`, `education`, `certifications`, `languages`,
|
|
52
|
+
`projects`, `recommendations`, and `volunteering` were typed as bare
|
|
53
|
+
`{ [key: string]: unknown }[]`; each entry now carries its known fields
|
|
54
|
+
(`name`, `endorsement_count`, `company`, `title`, and so on) intersected with
|
|
55
|
+
the same open index signature. Each field's description states where the
|
|
56
|
+
shape came from: these are declared from the classic profile's live-measured
|
|
57
|
+
shape for the same underlying section, not from a Recruiter- or Sales
|
|
58
|
+
Navigator-specific capture, so confirm field-for-field against a real
|
|
59
|
+
response before treating an inferred or absent field as fact.
|
|
60
|
+
- **Every paginated endpoint's 400 description now names a malformed cursor.**
|
|
61
|
+
An undecodable cursor is rejected with a 400 rather than silently serving
|
|
62
|
+
page 1. Documentation only; the response types are unchanged.
|
|
63
|
+
|
|
12
64
|
## [0.21.0] - 2026-08-13
|
|
13
65
|
|
|
14
66
|
Regeneration against the deployed, served OpenAPI document at server commit
|