# Changelog

Every Nextly release, newest first: what changed, and what its notes ask you to do before you upgrade.

[RSS](https://nextlyhq.com/changelog/feed.xml) · [Watch releases on GitHub](https://github.com/nextlyhq/nextly/releases)

## [0.0.2-alpha.78](https://nextlyhq.com/changelog/0.0.2-alpha.78)

15 Nov 2026 · Newest · Before you upgrade: No steps listed

- [A page of any type can carry an FAQ section in its structured data, declared by its route or for its whole content type.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.78)
- [The SEO plugin can state the site's X account on every page, and gives a site's own sitemap the date a page's content last changed, which an SEO-only save no longer moves.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.78)
- [On Vercel, the PostgreSQL and MySQL adapters default to a small database pool: at most 3 connections, none kept open, and idle ones closed after 5 seconds.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.78)

## [0.0.2-alpha.77](https://nextlyhq.com/changelog/0.0.2-alpha.77)

14 Nov 2026 · Before you upgrade: No steps listed

- [An admin session no longer ends when the browser's network address changes.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.77)
- [nextly migrate:status names every registry row that differs from the newest applied migration's record of it, and says to run nextly migrate.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.77)
- [The SEO plugin's address record catch-up no longer leaves a database transaction open on a serverless host such as Vercel.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.77)

## [0.0.2-alpha.76](https://nextlyhq.com/changelog/0.0.2-alpha.76)

13 Nov 2026 · Before you upgrade: No steps listed

- [In the admin, restoring a version puts its fields back into the editor as unsaved edits, and nothing is stored until you save.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.76)
- [A production start no longer creates or changes a table or writes the registry, and next build no longer writes to the database: run nextly migrate before serving.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.76)
- [The admin has a Content overview at /admin/content: each collection you can open, with its entries, drafts and last edit, and who last edited each Single.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.76)

## [0.0.2-alpha.75](https://nextlyhq.com/changelog/0.0.2-alpha.75)

12 Nov 2026 · Before you upgrade: No steps listed

- [The server no longer waits for Nextly to start before it answers requests.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.75)
- [One command adds a plugin to a site: nextly plugins add installs the package, registers it in nextly.config.ts and applies its schema.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.75)
- [The admin is served as not listable by search engines, with or without a plugin that manages search.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.75)

## [0.0.2-alpha.74](https://nextlyhq.com/changelog/0.0.2-alpha.74)

11 Nov 2026 · Before you upgrade: No steps listed

- [An editor is told when someone else changes the document they hold, and a save over a newer copy opens a conflict dialog instead of overwriting it.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.74)
- [Documents can be added to a release from inside it, across every collection and Single.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.74)
- [nextly migrate checks each applied migration file against the checksum it recorded, and stops before changing anything when one was edited.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.74)

## [0.0.2-alpha.73](https://nextlyhq.com/changelog/0.0.2-alpha.73)

1 Nov 2026 · Before you upgrade: No steps listed

- [A release's page names its documents by title, grouped by collection, and says whether each goes live or comes down and whether it is ready.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.73)
- [A document can be scheduled to publish from the editor's publish button.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.73)
- [A bulk or batch write is limited to the entries its access rule's filter matches, as a write to one entry is.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.73)

## [0.0.2-alpha.72](https://nextlyhq.com/changelog/0.0.2-alpha.72)

27 Oct 2026 · Before you upgrade: 14 steps · Security · Run `nextly migrate`

- [Security: the MCP server SDK, nodemailer, undici and fast-uri move past their published advisories. Apps that send email over SMTP need nodemailer 10.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.72)
- [New projects ship the route that serves local uploads under `next start`.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.72)
- [A code access rule now narrows what a role allows: it no longer lets in a signed-in user who lacks the permission.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.72)

<!-- release-notes -->

- Security: upgrade to pick up the MCP server SDK 2.3.1, nodemailer 10.2.1, undici 7.30.1 and fast-uri 3.1.9
- Security: password fields inside field groups are now stored hashed, and no read returns a password
- Security: publishing several languages at once asks the publish rule for each language
- Security: `GET /me/capabilities` names only what the caller may read

<!-- /release-notes -->

## [0.0.2-alpha.71](https://nextlyhq.com/changelog/0.0.2-alpha.71)

25 Oct 2026 · Before you upgrade: 2 steps · Security

- [Security: zod moves to 4.6.7 and DOMPurify to 3.4.17.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.71)

<!-- release-notes -->

- Security: upgrade to pick up zod 4.6.7 and DOMPurify 3.4.17

<!-- /release-notes -->

## [0.0.2-alpha.70](https://nextlyhq.com/changelog/0.0.2-alpha.70)

25 Oct 2026 · Before you upgrade: 1 step · Security

- [An anonymous create, update or delete now needs an access rule that allows it.](https://github.com/nextlyhq/nextly/releases/tag/v0.0.2-alpha.70)

<!-- release-notes -->

- Security: an anonymous create, update or delete now needs an access rule that allows it

<!-- /release-notes -->

## [0.0.2-alpha.69](https://nextlyhq.com/changelog/0.0.2-alpha.69)

24 Oct 2026 · Before you upgrade: 30 steps · Security · Run `nextly migrate`

- In production, the web setup asks for a one-time setup token, printed in the server log, before it creates the first admin.
- Role-based permissions for each collection and action, plus field-level read and write rules in code, on a collection’s or single’s fields, fields inside field groups included.

## [0.0.2-alpha.68](https://nextlyhq.com/changelog/0.0.2-alpha.68)

19 Oct 2026 · Before you upgrade: 4 steps · Run `nextly migrate`

- The Visual Page Builder opens as a screen of its own, at the page’s own address.
- With the rate limit on (the default), every REST request now counts against it, the admin API included.

## [0.0.2-alpha.67](https://nextlyhq.com/changelog/0.0.2-alpha.67)

18 Oct 2026 · Before you upgrade: 1 step · Run `nextly migrate`

- Adding Nextly to an existing Next.js app now installs everything it needs and finishes, on npm, pnpm, Yarn and Bun.
- New command: `nextly users:clear-plaintext-passwords`. Earlier releases stored some passwords as typed instead of hashing them. Such a value never let anyone sign in, but it is readable in the database and its backups.

## [0.0.2-alpha.66](https://nextlyhq.com/changelog/0.0.2-alpha.66)

14 Sep 2026 · Before you upgrade: No steps listed

- Saving a published page no longer puts the edit live. Pages now keep a working draft.
- Every sortable table in the admin can be reordered from the keyboard, and a screen reader is told what is being moved.

## Earlier releases

Releases before 0.0.2-alpha.66 are listed in [Nextly's changelog on GitHub](https://github.com/nextlyhq/nextly/blob/main/packages/nextly/CHANGELOG.md).

13 releases on this page, newest first.
