v2.1.0

What's Changed

• release: litedbmodel 2.1.0 — bc 0.8.0 + declare-via-BC + 統一 cross-lang bench (supersedes #62) by @foo-ogawa in #68

Full Changelog: v2.0.2...v2.1.0

v2.0.2

What's Changed

• fix(scp): close re-audit correctness gaps — H1 PG cast, M2 find-filter guard, M4 gate, L3/L4 fallbacks by @foo-ogawa in #49
• rust runtime perf: statement-template borrow + single-buffer render + single-node fast-path by @foo-ogawa in #50
• Release 2.0.2 — bc 0.5.0, SQL-type system, typed-native READ codegen (SQL parity), docker PG/MySQL bench by @foo-ogawa in #61

Full Changelog: v2.0.1...v2.0.2

v2.0.1

What's Changed

• litedbmodel 2.0.1 — SQL parity degradation repair + full v2 completeness by @foo-ogawa in #48

Full Changelog: v2.0.0...v2.0.1

v2.0.0

What's Changed

• fix: trigger publish after GitHub Release workflow completes by @foo-ogawa in #20
• litedbmodel v2.0.0 — SCP 統合 / 多言語 CQRS（breaking, epic #29） by @foo-ogawa in #39

Full Changelog: v1.2.10...v2.0.0

v1.2.10

What's Changed

• chore: split GitHub Actions into CI, audit remediate, and release workflows by @foo-ogawa in #17
• fix: correct npm-audit-remediate workflow YAML parsing by @foo-ogawa in #18
• chore: bump version to 1.2.10 by @foo-ogawa in #19

Full Changelog: v1.2.9...v1.2.10

v1.2.9

Security fixes

• Update esbuild 0.27 → 0.28.1 (GHSA-g7r4-m6w7-qqqr)
• Override js-yaml to 4.2.0 (GHSA-h67p-54hq-rp68)
• Update vite to 8.0.16 (GHSA-v6wh-96g9-6wx3, GHSA-fx2h-pf6j-xcff)
• npm audit: 0 vulnerabilities

v1.2.8

Changes

• Reposition as "Production-safe SQL-first Database Access Layer for AI-assisted development"
• Add Why AI-friendly? and Production Safety Features sections to README
• Add DX redefinition note and philosophy-first comparison table
• Create SECURITY.md with trust boundaries, safe/unsafe API patterns, and vulnerability reporting
• Add JSDoc security warning to sql.raw() (addresses LDB-01 from security audit)
• Add docs/README_REVIEW.md with review notes

v1.2.7

Changes

• Connection error auto-retry: transaction() and non-transactional execute()/executeWrite() now detect stale/broken connections and retry once automatically (PostgreSQL + MySQL)
• keepAlive support: DBConfig now accepts keepAlive and keepAliveInitialDelayMillis for TCP keepalive on pooled connections (recommended for serverless/Lambda environments)
• Pool error handler: Idle client disconnections no longer crash the Node.js process
• isConnectionError() utility: Exported for custom retry logic

Connection error patterns detected

• PostgreSQL: Connection terminated unexpectedly, Connection terminated, Client has encountered a connection error
• MySQL: Connection lost, This socket has been ended by the other party, PROTOCOL_CONNECTION_LOST
• Network: ECONNRESET, ECONNREFUSED, EPIPE, EAI_AGAIN

Closes #13

v1.2.6

Changes

• fix: トランザクションエラー後のコネクションをプールに返却せず破棄するように変更
  • DBConnection.release(error?) にオプション引数を追加
  • PostgreSQL: PoolClient.release(err) でコネクション破棄
  • MySQL: connection.destroy() でコネクション破棄
  • ROLLBACK 失敗時も元のエラーを保持（try/catch で保護）
  • query_timeout 後の dirty connection がプールに戻る問題を防止

v1.2.5

Changes

• fix: sql.raw() inside Model.find() conditions no longer appends = TRUE to the SQL expression (#10)
  • compileCondition() now detects SQL expression keys (containing spaces) and returns them as-is
  • e.g., updated_at >= NOW() - INTERVAL '180 days' is no longer corrupted to ... = TRUE