@pidgeon-ai/sdk 1.19.0 → 1.19.2
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 +14 -0
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +2 -2
- package/dist/index.d.ts +2 -2
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,20 @@ 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.19.2 — what `/raw` answers
|
|
11
|
+
|
|
12
|
+
The description of `GET /messages/{id}/raw` said it 404s once the original
|
|
13
|
+
has aged out. It does not: it answers a rebuild from the stored message,
|
|
14
|
+
marked `X-Pidgeon-Reconstructed: true`, and received mail is the archived
|
|
15
|
+
original until then. Wording only; no shape moves.
|
|
16
|
+
|
|
17
|
+
## 1.19.1 — the default wait is under a minute
|
|
18
|
+
|
|
19
|
+
`GET /messages/await` waits 50 seconds when no `timeout` is given, down
|
|
20
|
+
from 60. Clients that give up on a request at 60 seconds — the TypeScript
|
|
21
|
+
Agents SDK, Claude Code's MCP client — failed the default wait exactly when
|
|
22
|
+
no message came. An explicit `timeout` up to 280 behaves as before.
|
|
23
|
+
|
|
10
24
|
## 1.19.0 — every status is declared, and Python raises
|
|
11
25
|
|
|
12
26
|
The contract declares every status a route can answer with, read off the
|