
import { Badge } from "zudoku/ui/Badge";

# Changelog

The API follows semantic versioning on a single set of routes. Minor versions
only add fields, so existing integrations keep working without changes. The
current version is in the `info.version` of the [API Reference](/api).

## 1.2.0

<Badge variant="secondary">Behavior change</Badge>

**Meeting `status` now reflects what is happening right now.** `status` is
`live` while a meeting is in session, `cancelled` if it was cancelled, and
`null` otherwise.

Use `date` to tell upcoming meetings from past ones, for example
`date: { gte: <now> }` for upcoming.

## 1.1.0

<Badge variant="secondary">Non-breaking</Badge> <Badge variant="outline">Additive</Badge>

**Portal links on every record.** Responses that describe something a person
can open on the government's public portal now include a `portalUrl`:

- Meetings, boards, board categories, members, topics (legislative items),
  and the parent record of a document search hit.
- Transcript search hits link to the meeting, and each matching segment links
  to the recording cued to that moment.

Use `portalUrl` as the user-facing link instead of assembling one from an
`id`. The field is always present where it is documented, so it is safe to
rely on.

**Transcript search** responses now pass through the gateway's response
shaping like every other route.

Field descriptions in the API Reference were revised; no request parameters,
paths, or existing response fields changed.

## 1.0.0

<Badge variant="outline">Initial release</Badge>

Initial public release: meetings, agendas, legislation, documents, boards and
seats, and recordings, plus the MCP server at `/mcp`.
