What shipped,
and when.
- WorkflowAgentsNotifications
The workflow layer
Mark a document reviewed or implemented, leave a note anchored to a heading, and watch a whole corpus move across a board you can filter with a URL you send to somebody. Status and notes drift against the content itself rather than against a timestamp, so a rewrite is never readable under a badge that still says validated — and an agent may claim that feedback is addressed, but only a person may close it.
- AgentsSourcesSecurity
The agent surface
One stateless endpoint an agent points at, with a key scoped to a single project and owned by the organization rather than by whoever created it — so a pipeline survives somebody changing team. Summaries landed with it, keyed to the content they summarise so they report drift the moment a document changes, off by default and audited when switched on. GitLab became a source in the same release, self-managed instances included.
- Security
Signing in without GitHub, and the audit log
Email and a password, minting the same session the GitHub callback mints — no second session format, so no second expiry rule and no second revocation story. Beside it, every change recorded with who and when, written inside the same transaction as the change it describes, and an IP allowlist for organizations that want one.
- Billing
Plans, seats, and paying for it
Checkout, the customer portal, and one place a subscription's state ever changes: the webhook reads the subscription back rather than trusting the event, because somebody can close the success page and still be charged. Seats are billed on the period's high-water mark, so four people added mid-month are paid for and removing them the day before the invoice is not a discount.
- SecuritySources
Organizations, teams and private repositories
Membership is the organization; access is the project. Joining hands out no documents — an invitation carries an intent and grants nothing until it is accepted, and somebody in no team with no grant reads nothing at all. Private repositories arrived with it, read through a per-repository app whose tokens are minted on demand and never written down. The end of the beta.
- Reading
Search, projects, and the lit path
Full-text search across a whole corpus, repositories grouped into projects, and the sidebar tracing the path to the document you are reading, lit in the accent gradient. It is the signature element of the interface and the reason everything around it stays quiet.
- SourcesReadingSecurity
Staying in step with the repository
A verified webhook, a queue and a worker that drains it: repositories are never cloned, and a file whose content hash has not moved is skipped entirely. Markdown is stored raw and rendered on read — sanitized server-side on an allowlist, with mermaid diagrams and syntax highlighting reading their colours from the live theme rather than shipping a stock one.
- Reading
Docs roots, titles and ordering, worked out
Where the documentation lives, what each page is called, what order the pages go in and which files are noise rather than docs — all inferred from the repository as it already is. If a reader ever needs a config file the product has failed, so these rules are the product rather than helpers around it.
- Reading
Reading a repository's documentation, with no configuration
Point it at a repository and the folder structure is the navigation. No manifest, no sidebar to maintain, no ordering file to keep in step with the tree. Everything in every release after this one is in service of that sentence.
This page lists releases, not every change — a release carries far more than the one line describing it. The full list of what it does is a better answer than a longer changelog.