Skip to content

Releases: cstion-ai/cstion

v0.1.1 — Maintenance toolchain upgrade

Choose a tag to compare

@cstion-ai cstion-ai released this 26 Jul 22:53
b280574

Highlights

  • upgrades Zod to 4.4.3, TypeScript to 7.0.2, tsx to 4.23.1, and aligns type definitions with Node.js 22
  • updates commit-pinned checkout and setup-node actions
  • enforces 90% line, 80% branch, and 85% function coverage in CI
  • validates configuration failures through stable structured Zod issue data

Verification

The tagged merge commit passed the Node.js 22 test/typecheck/build job, the PostgreSQL 16 integration suite, CodeQL, dependency review on PR #12, and a high-severity dependency audit.

Known limitation

This remains a reference implementation, not a production-ready service. Production startup intentionally fails while the real CRM and Google Sheets adapters are unavailable. No production deployment or public adoption is claimed.

Full changes: v0.1.0...v0.1.1

v0.1.0 — Public baseline

Choose a tag to compare

@cstion-ai cstion-ai released this 26 Jul 01:34
0281609

Public baseline

This first release publishes the Apache-2.0 TypeScript and PostgreSQL reference implementation reviewed in PR #4.

Included

  • authenticated, size-limited Kakao webhook ingestion
  • PostgreSQL-backed event leases, customer identities, and idempotent booking leads
  • recorded legacy-schema migration with advisory locking
  • concurrency-safe customer identity ownership
  • HMAC-protected OAuth state cookies and typed Kakao token-exchange failures
  • redacted failure logging and fail-closed production composition
  • contributor, governance, security, support, and threat-model documentation

Verification

The release commit passed:

Reproduce locally with npm ci, npm test, npm run typecheck, npm run build, and npm audit --audit-level=high. With a disposable PostgreSQL database, run DATABASE_URL=... npm run test:postgres.

Known limits

This release is not production-ready. CRM and Google Sheets adapters are still fakes and production startup intentionally fails closed. It does not include edge rate limiting, a server-side one-time OAuth state store, backup/restore rehearsal, sustained-load evidence, or real provider integration tests. No public adoption or deployment usage is claimed.