Repository navigation
3ngram 1.9.1
3ngram v1.9.1
Patch: two dependency security fixes. v1.9.1 is the first published 1.9
release. The v1.9.0 tag exists, but its release run stopped at the image
scan before anything was published, so no 1.9.0 artifact exists on npm or
GHCR. Everything in the v1.9.0 notes ships in this release.
Changes
- zod 4.6.6 (#347, CVE-2023-54404: denial of service via unbounded array
validation). Every package that pins zod moves from 4.6.5:@3ngram/schema,
@3ngram/config,@3ngram/sdk,@3ngram/serverand the3ngramCLI. - body-parser 2.4.0 (#347, CVE-2026-111181: denial of service via an
unhandled decompression stream error). It is transitive under express
5.3.0 and moved through the workspace advisory override. Because 2.4.0 was
published inside the 7-day registry cooldown, it is a reviewed
exact-versionminimumReleaseAgeExcludeentry until it matures. The 413 /
415 / 400 mapping for rejected request bodies is unchanged.
Compatibility
- Runtime pin lockstep. Consumers that pin
zodexactly next to
@3ngram/schemaor@3ngram/sdkmust move to 4.6.6 together. A second zod
copy splits the schema types. - Upgrading from 1.8.x? Read the v1.9.0 notes first: they cover
the new MCP output fields, therevisedispositions and the newreaffirm
event kind.
Operations
- From 1.8.x, apply migrations 0039–0041 before starting the new server (see
the v1.9.0 notes). There is no new migration in this patch. - No configuration change.
Immutable container reference
ghcr.io/b3dmar/3ngram@sha256:e6bae3efdd20935cea81eafac77ff86ed99b9b08508e55a74061e92b17dad68d