Skip to main content

Release Notes

This page is auto-updated from platform release events — every time a release lands in production, the coordinator writes a row to the release_events table and Phase 2 wiring will publish the row here. Until Phase 2 lands, use this page as the anchor point for the feed; the same data is available today from the support_get_recent_release_notes tool the Support Bot exposes.

The feed shows platform-facing changes (coordinator, kpack, healer, BuildRepairAgent, console). Application-facing changes you ship yourself do not appear here — those live in your own app's build history.

What "released" means​

A release event is written when:

  • a coordinator or agent image rolls out to production
  • a database migration succeeds in the production Flyway pipeline
  • a new console version is published to console.clue2.app
  • an MCP server package is published to PyPI

The row carries the component, the version or migration id, the change summary, and the operator or automation that triggered the roll-out.

Recent releases​

Populated automatically once Phase 2 wiring is enabled. Until then this section stays intentionally empty rather than showing stale hand-curated entries — pull the same data live via the Support Bot's support_get_recent_release_notes tool.

2026-09-02 — Privacy page + website chatbot prep​

  • New Privacy page covering the marketing site and the upcoming "How can I help you?" website chatbot. The chatbot section is at /privacy#chat and lists what the widget collects, how long we keep it, which third parties see it, the lawful basis, and how to ask for deletion.
  • Site now carries the widget's copy strings in one place so the privacy page, the widget footer (arriving in a later release), and the escalation form stay in sync as wording evolves.
  • Widget itself is not yet enabled. Rendering is behind a feature flag that defaults off until the launch checklist is signed off; if the widget is disabled or the endpoint is offline, visitors see a short "temporarily unavailable" message and can still reach us via the contact form or support@clue2app.ai.

Where the data lives​

LayerWhat it holdsAccess
coord.release_events (V52)Every release row: component, version, summary, operator, timestamp.Platform-internal; queried by the feed generator.
support_get_recent_release_notes (MCP tool)Reads the feed on demand, filtered by your account's visible components.Via the Support Bot.
This pageThe auto-generated public view.Public read.

Retention​

Release events are retained for the life of the platform — they double as change-management evidence for SOC 2 CC8.1. The change-management review flow that produces the rows is documented in the platform's internal Change Management Runbook (available on request today; slated for public docs once reviewed).