@pidgeon-ai/sdk 1.39.0 → 1.40.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 +11 -0
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +37 -6
- package/dist/index.d.ts +37 -6
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,17 @@ the two would publish a release for every unrelated product deploy.
|
|
|
7
7
|
Semver applies to **this package's own surface** — the exported names, the
|
|
8
8
|
call shapes, the result shape — not to the API behind it.
|
|
9
9
|
|
|
10
|
+
## 1.40.0 — every key states its scope
|
|
11
|
+
|
|
12
|
+
- `keysCreate` requires `access`, and takes `reaches_all` beside
|
|
13
|
+
`identity_ids` and `pod_id`: one of the three is the key's reach. A key
|
|
14
|
+
cannot ask for `reaches_all`; an owner chooses it in the dashboard.
|
|
15
|
+
- `podsCreate`'s `key` requires `access`.
|
|
16
|
+
- Both answers may carry `warnings` beside `data`. Until 26 November 2026 the
|
|
17
|
+
API still takes a mint without `access` — the new key gets the calling
|
|
18
|
+
key's level — and says so there; from that date it is a 400 with
|
|
19
|
+
`field: "access"`. Code built against this version never sees it.
|
|
20
|
+
|
|
10
21
|
## 1.39.0 — what happened to a send
|
|
11
22
|
|
|
12
23
|
- Every `Message` carries `delivery`: `state`, the worst any recipient has
|