Skip to content

Releases: AdaInTheLab/lab-api

v0.7.0 — Admin Stabilization

09 Jan 18:36
5960cd9

Choose a tag to compare

Pre-release

This release establishes a stable administrative foundation ahead of formal API versioning.

Admin token routes are now registered in the main application (not test-only), ensuring that admin surfaces have real, reachable endpoints in local development and production environments. Route wiring has been aligned between test and non-test apps to prevent drift.

No new token workflows or versioned API boundaries are introduced in this release. The goal is stability, correctness, and a known-good baseline that frontend and future tooling can rely on.

This release serves as a pre-versioning anchor for upcoming API evolution.

v0.2.0 — Ledger Era + Canonical API Base

01 Jan 14:56

Choose a tag to compare

Breaking

  • API base is now https://api.thehumanpatternlab.com.
  • Removed /api path prefix from canonical routes.
    • Example: /lab-notes (new) instead of /api/lab-notes (old).
  • Main site legacy /api/* routes are deprecated and redirect to the API subdomain.

Database

  • Refactored persistence to the Ledger model.
    • Ledger becomes the canonical source of truth for note storage and mutation history.
    • Improves auditability and enables future CLI automation workflows.

Notes API

  • Lab Notes endpoints continue to support list + detail retrieval while backed by the Ledger model.
  • Response shape remains compatible with existing UI normalization (fields unchanged unless noted).

Ops / Deployment

  • Production routing standardized: website on thehumanpatternlab.com, API on api.thehumanpatternlab.com.
  • Reduced ambiguity between static site routes and API routes.

v0.1.1 – Safe DB schema migration

29 Dec 13:43
64c337f

Choose a tag to compare

Pre-release

This release hardens the database layer to evolve safely without data loss.

Added

  • Idempotent schema migration for lab_notes
  • Lightweight schema version tracking via schema_meta
  • Startup logging when schema changes are applied

Changed

  • Centralized database migration logic into a dedicated module
  • Made database bootstrap resilient to existing and older schemas

Notes

  • No API behavior changes
  • Safe to deploy over existing databases