What kuzzleio/kuzzle shipped
Written by FoxPlug from the repository's own releases; not affiliated with Kuzzle. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/kuzzleio/kuzzle; Kuzzle did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of September 28, 2026
What shipped
- Released v2.59.0 with collection write locks and unmanaged indices, two opt-in storage primitives that enable the mapping-migration plugin to rebuild collections without breaking changes. Release
- Released v2.58.0 taking API contract types from the new kuzzle-types package, unifying type definitions between server and SDK without breaking changes. Release
- Released v2.57.0, the first Kuzzle built entirely in TypeScript strict mode with no behavior changes, including API key deletion by fingerprint and cluster sync message retransmission. Release
- Added collection write locks and unmanaged indices to storage, generic opt-in primitives with no effect until explicitly used by code like the mapping-migration plugin. Pull request #2962
- Upgraded kuzzle-logger to 1.5.0, changing how errors are logged to include name, message, stack, cause, and custom properties like KuzzleError id. Pull request #2967
- Fixed plugin ESClient constructor to follow the configured Elasticsearch major version, so plugins on Elasticsearch 8 deployments now receive 8.x clients instead of always receiving 7.x. Pull request #2947
- Refactored RoleDefinition to build on the API contract, reconciling duplicate types between server and SDK without breaking changes to public types. Pull request #2959
- Added v3-breaking-changes.md documenting 90 items across 9 categories that Kuzzle 2 keeps only to avoid breaking changes, serving as the backlog for v3. Pull request #2961
- Introduced ADR-0003 proposing storage engines as installable drivers, an npm package implementing a StorageDriver contract selected by configuration. Pull request #2948
- Fixed API key deletion by key or fingerprint on upgraded installs, which was returning 404 for every key including those created after upgrade. Pull request #2942
Why it matters
Kuzzle 2.59.0 ships new storage primitives enabling safer collection migrations, while 2.57.0 reached TypeScript strict mode with no behavior changes, and 2.58.0 unified type definitions with the SDK. These releases maintain backward compatibility while preparing infrastructure for future enterprise features and v3.
Changelog entry
- Storage: collection write locks and unmanaged indices Release
- Take the API contract types from kuzzle-types Release
- ApiKeys: allow an api key to be deleted by the key itself or its fingerprint Release
- Ci: ratchet implicit any, and count as unknown as any Release
- Cluster: retransmit lost sync messages before evicting Release
- Logger: upgrade kuzzle-logger to 1.5.0 Pull request #2967
- Plugin: context.constructors.ESClient follows the configured major version Pull request #2947
- Bug: API keys deletable by key or fingerprint on upgraded installs Release
- Bug: logstash access logs carry the request headers once Release
- Bug: published typings compile without dev dependencies Release
- Storage: mark the IndexCache maps readonly Pull request #2963
Kuzzle 2.59.0 out now: collection write locks and unmanaged indices for safer storage operations. 2.57.0 is the first fully TypeScript strict build. 2.58.0 shares types with the SDK.
Three new Kuzzle releases this week: 2.59.0 with collection write locks and unmanaged indices for safer migrations; 2.57.0 as the first fully TypeScript strict build with zero behavior changes; 2.58.0 unifying API contract types with kuzzle-types. All maintain backward compatibility while strengthening the platform.
Week of September 14, 2026
What shipped
- Both Elasticsearch services moved to strict TypeScript and adopted into the ratchet guard in step 12 K3. Pull request #2802
- API keys can now be deleted by _id, fingerprint, or key value in security/deleteApiToken and auth/deleteApiToken actions. Pull request #2683
- Fixed TD-69: a node that loses the mappings-import race now refuses to boot instead of continuing with stale state. Pull request #2786
- Fixed TD-70: removed artificial order pinning from an unordered search test that was causing flaky assertions. Pull request #2787
- Sprint 8 J3b completed: node.js converted to TypeScript, the last JavaScript file in lib/cluster. Pull request #2792
- Fixed CI ratchets for implicit-any and casts to fail closed when the measuring tool cannot run. Pull request #2795
- Fixed preflight conversion reminder to see uncommitted work, closing TD-66. Pull request #2796
- Fixed docker unit runner to stop rewriting the host's
node_modulesduring bind-mounted test execution. Pull request #2797
Why it matters
The project continues TypeScript migration with strict type checking spreading from Elasticsearch services into core libraries, while fixing critical cluster startup races and API key deletion edge cases discovered during the conversion process. CI tooling was hardened to prevent false negatives in type safety gatekeeping.
Changelog entry
- Fix(types): Elasticsearch services elasticsearch.ts strict-clean and adopted in step 12 K3 Pull request #2802
- Feat(apiKeys): deleteApiToken actions accept _id, fingerprint, or key to select api key Pull request #2683
- Fix(kuzzle): node losing mappings-import lock now refuses to boot, closes TD-69 Pull request #2786
- Fix(tests): removed artificial order pinning from unordered search test, closes TD-70 Pull request #2787
- Refactor(cluster): node.js converted to TypeScript in sprint 8 J3b Pull request #2792
- Fix(ci): implicit-any and casts ratchets now fail closed when measuring tool fails Pull request #2795
- Fix(ci): preflight conversion reminder sees uncommitted work, closes TD-66 Pull request #2796
- Fix(ci): docker unit runner no longer rewrites host
node_modulesduring bind-mount test Pull request #2797
Step 12 slice K3 ships: Elasticsearch services now strict-clean and adopted. API keys delete by _id, fingerprint or key. Fixed cluster startup race (TD-69) and flaky search test (TD-70).
Kuzzle advances TypeScript migration: Elasticsearch services now strict-typed and protected by ratchets. Simultaneously shipping API key deletion flexibility, a fix for cluster startup failures when nodes lose the mappings-import race, and hardened CI tooling that prevents type safety regressions. lib/cluster is now entirely TypeScript.