Mem0 has shipped Node SDK release ts-v3.0.1, a small but important patch that fixes incorrect telemetry version reporting across its JavaScript package. Until this update, telemetry events emitted by both SDK telemetry clients could report outdated 2.x version strings even when users had installed a 3.x package. This release ensures the reported client version now always matches the actual installed package version.
The core fix replaces hardcoded version strings inside the telemetry modules with a build-time injected constant sourced from package.json. In practice, Mem0 now uses esbuild define replacement so the correct SDK version is embedded directly into the bundled output during the build process.
This affects both telemetry paths in the package: MemoryClient and the OSS Memory implementation. Previously, the telemetry files contained stale values such as 2.1.36 and 2.1.34, which meant every telemetry event could misreport the SDK version after the package had already moved into the 3.x line.
The release also includes a new ambient constant declaration in mem0-ts/src/global.d.ts, updates to mem0-ts/tsup.config.ts so the package version is injected into both client and OSS builds, and a matching setup in mem0-ts/jest.setup.ts so test environments continue to resolve the same version symbol correctly.
Although this is a patch release, it improves the reliability of telemetry data used for product diagnostics, usage analysis, and support workflows. When SDK events report the wrong client version, debugging becomes slower and release adoption becomes harder to measure accurately.
The implementation choice is also notable from an engineering perspective. Because the version is substituted at bundle time, the fix avoids runtime file reads and does not depend on importing package.json in production bundles. That keeps the package lean while making telemetry metadata trustworthy.
For teams building memory-enabled AI applications on Node.js, ts-v3.0.1 is mainly a maintenance upgrade rather than a feature release. Still, it closes an instrumentation gap that could affect observability and support accuracy across deployments.
Official Source: https://github.com/mem0ai/mem0/releases/tag/ts-v3.0.1