Lithium Core

v0.0.5 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 6d Relational Databases

✓ No known CVEs patched

✓ No known CVEs patched in this version

Topics

ai ai-agents ai-memory claude-code cursor hierarchical

+10 more

ltree mcp postgresql llm storage-engine structured-context structured-data typescript versioned versioned-storage

ReleasePort's take

Moderate signal

editorial:auto 2d

In @lithium-ai/[email protected] the createEntry function replaces insert, providing atomic entry handling.

Why it matters: If your code uses insert in @lithium-ai/core, update to call createEntry; failure causes runtime errors after upgrade (severity 70).

AI summary

createEntry replaces insert and adds atomic entry handling

Type	Severity	Summary	CVE
Breaking	High	createEntry replaces insert in @lithium-ai/[email protected] createEntry replaces insert in @lithium-ai/[email protected] Source: llm_adapter@2026-06-01 Confidence: high	—
Feature	Medium	Added txResult with sql.begin() for rollback in @lithium-ai/[email protected] Added txResult with sql.begin() for rollback in @lithium-ai/[email protected] Source: llm_adapter@2026-06-01 Confidence: high	—
Feature	Medium	Added txResult with db.transaction() for rollback in @lithium-ai/[email protected] Added txResult with db.transaction() for rollback in @lithium-ai/[email protected] Source: llm_adapter@2026-06-01 Confidence: high	—

Full changelog

@lithium-ai/[email protected] — createEntry replaces insert, atomic entry + version 1
@lithium-ai/[email protected] — txResult with sql.begin() for rollback on failure
@lithium-ai/[email protected] — txResult with db.transaction() for rollback on failure
Unit tests updated, integration tests passing

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track Lithium Core

Get notified when new releases ship.

About Lithium Core