Skip to content

CHANGELOG.md

Latest commit

 

History

History
145 lines (114 loc) · 5.64 KB

CHANGELOG.md

File metadata and controls

145 lines (114 loc) · 5.64 KB

Changelog

All notable changes to ThinkWatch are recorded here. Format follows Keep a Changelog; from 1.0.0 onwards versioning follows SemVer.

Until 1.0.0, any 0.y bump may include breaking changes — see the notes under each release. Operators upgrading inside the 0.x line should read the section for every intermediate version, not just the target.

Unreleased

Added

  • (nothing yet)

Changed

  • (nothing yet)

Fixed

  • (nothing yet)

Removed

  • (nothing yet)

Security

  • (nothing yet)

1.0.1 — 2026-05-27

Release-pipeline validation. No product change — the published binary, REST surface, MCP wire shapes, and audit semantics are identical to v1.0.0. Operators pinning 1.0.0 have no reason to bump; those tracking :latest move forward.

Changed

  • Release workflow — arm64 image builds now run on a native arm64 runner (ubuntu-24.04-arm) instead of QEMU emulation. v1.0.0's server image build took 1h24m; this should drop to ~10 min. Multi-arch manifest assembled by a new merge job via docker buildx imagetools create.
  • Node 24 opt-in — workflow sets FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true so all actions/* + docker/* run on Node 24 ahead of GitHub's 2026-06-02 forced cutover.

1.0.0 — 2026-05-27

Stability commitment. No code delta since 0.5.0 — this tag marks the point at which the API surface becomes a SemVer commitment.

Changed

  • Versioning policy — from this tag onwards every breaking change (REST routes, MCP wire shapes, audit-row JSON keys, database schema, public Rust APIs in published crates) requires a major bump. Operators chasing the :latest tag on the GHCR images can do so without surprise.

Notes

  • Docker images cut at this tag receive :latest for the first time — the release workflow suppresses :latest on 0.x and pre-release tags. Pin the version in production rather than tracking :latest unless you have a controlled rollback path.

0.5.0 — 2026-05-26

First public beta. The product surface is stable enough to deploy against, but the API contract is not yet committed — expect breaking changes in 0.6.x and beyond as the run-up to 1.0.0 narrows the surface. Operators running this version against real traffic should pin the image digest and read every subsequent release note.

Highlights

  • AI gateway (:3000) — OpenAI / Anthropic / Google / Azure OpenAI / AWS Bedrock with weighted multi-route failover, circuit breakers, semantic response cache (Redis-backed), SSE streaming with PII restore on the wire.
  • MCP gateway — per-user OAuth + static-token + admin-shared credential modes, response cache with prefix-based invalidation, per-server circuit breakers keyed by UUID (so a rename or recreate doesn't inherit stale state).
  • Audit pipeline — bodies up to audit.body_max_bytes land inline in ClickHouse; oversize bodies offload to S3-compatible object storage (RustFS / MinIO / AWS S3). Request and response bodies are PII-redacted before write; the bucket lifecycle rule is administered from the admin UI (audit.body_s3_lifecycle_days).
  • RBAC + identity — JWT access tokens, refresh tokens, OIDC SSO, TOTP, recovery codes. Permissions evaluated on every request from a Redis-cached + DB-backed policy. Per-API-key limits + budgets enforced on the gateway hot path.
  • Observability — /metrics (Prometheus exposition, bearer- protected), /api/health (PG + Redis + ClickHouse + S3 deep probe), per-request x-trace-id, structured tracing.
  • Admin console (:3001) — React 19 + TypeScript + i18n (en/zh, perfect parity). Dashboard, traces, cost analytics, RBAC editor, MCP server CRUD, settings PATCH.

Quality

  • 675 unit + integration tests, gated on make precommit.
  • Five rounds of systematic bug audits (≈ 45 bugs fixed, ≈ 800 lines of legacy compat scrubbed) preceded this tag — see commits b0b5820 → dbfe9da for the full series.

Operations

  • Helm chart ships an opt-in ServiceMonitor (metrics.serviceMonitor.enabled=true) gated on the auto-generated METRICS_BEARER_TOKEN secret. Pair with kube-prometheus-stack for /metrics scraping.
  • deploy/grafana/dashboards/ — starter overview dashboard JSON plus a metric reference + minimal alert rule set in the README.
  • docs/operations/secret-rotation.md — JWT_SECRET online rotation and ENCRYPTION_KEY offline re-encrypt procedures.
  • docs/operations/backup-restore.md — PG + ClickHouse + S3 procedures with restore-order gotchas, cross-version compat notes, and a quarterly DR drill template.

Known limitations for 0.5.x

  • API surface NOT frozen — REST routes, MCP wire shapes, audit-row JSON keys, and database schema may change in any 0.x bump. SemVer kicks in at 1.0.0.
  • No online ENCRYPTION_KEY rotation — the documented procedure requires a brief downtime window. Online dual-key rotation is queued for 1.x.

Upgrade path from 0.1.0

The 0.1.0 series was never published; deployments running unreleased builds should: stop the gateway, run db/schema.sql against PostgreSQL, restart against this tag. The schema is idempotent end-to-end, so the apply is safe to repeat.