stitchkit 0.90.1 → 0.90.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 +18 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -15,6 +15,24 @@ additive**; the first breaking change landed in 0.10.0. Grep the file for
|
|
|
15
15
|
|
|
16
16
|
## [Unreleased]
|
|
17
17
|
|
|
18
|
+
## [0.90.2] — 2026-09-15
|
|
19
|
+
|
|
20
|
+
### Fixed
|
|
21
|
+
|
|
22
|
+
- **The guide's list of stitchkit's own error codes is held against the
|
|
23
|
+
registry.** `docs/guide/auth-and-errors.md` enumerates `STITCH_ERROR_STATUS`
|
|
24
|
+
in prose so it can be read, and the guide warns about itself that the
|
|
25
|
+
enumeration is what goes stale — naming one drift that stopped a consumer's
|
|
26
|
+
map compiling. Nothing stood behind the warning, and the list had gone stale
|
|
27
|
+
again: five of thirty-one codes were missing (`STREAM_ITEM_INVALID`,
|
|
28
|
+
`STREAM_FRAME_TOO_LARGE`, `STREAM_TERMINAL_MISSING`,
|
|
29
|
+
`STREAM_LIFETIME_EXCEEDED`, `GRAMMY_WEBHOOK_NOT_ACCEPTING`) while every gate
|
|
30
|
+
in the repository, `error-registry-completeness` included, stayed green. The
|
|
31
|
+
list is now complete and checked for set equality in both directions: a
|
|
32
|
+
missing code sends a reader hunting for a vocabulary that is already
|
|
33
|
+
published, an invented one sends them to map a code the framework never
|
|
34
|
+
throws.
|
|
35
|
+
|
|
18
36
|
## [0.90.1] — 2026-09-15
|
|
19
37
|
|
|
20
38
|
### Fixed
|
package/package.json
CHANGED