> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-forms/19.latest/release-notes.md). # Release Notes Get an overview of the things changed and fixed in each version of Umbraco Forms. In this section, we have summarized the changes to Umbraco Forms released in each version. Each version is presented with a link to the [Forms issue tracker](https://github.com/umbraco/Umbraco.Forms.Issues/issues) showing a list of issues resolved in the release. We also link to the individual issues themselves from the detail. If there are any breaking changes or other issues to be aware of when upgrading they are also noted here. {% hint style="info" %} If you are upgrading to a new major version, you can find information about the breaking changes in the [Version Specific Upgrade Notes](/umbraco-forms/19.latest/upgrading/version-specific.md) article. {% endhint %} ## Release history This section contains the release notes for Umbraco Forms 19 including all changes for this version. ### [19.0.0-rc1](https://github.com/umbraco/Umbraco.Forms.Issues/issues?q=is%3Aissue+label%3Arelease%2F19.0.0) (November 12th 2026) {% hint style="warning" %} This is a prerelease for testing. Don't use it on a production site. Forms 19.0.0-rc1 needs Umbraco CMS `19.0.0-rc1`. It's published to NuGet and npm as a prerelease. There's no version 19 of Umbraco Forms Deploy yet. Sites that use Umbraco Deploy, including Umbraco Cloud sites, can't use this release. {% endhint %} #### Umbraco CMS 19 support Forms 19 runs on Umbraco CMS 19 and .NET 11. #### Breaking changes Forms 19 removes code and front-end features that were announced for removal: * Client-side validation with jQuery Validation, in favor of ASP.NET Client Validation ([announcement](https://github.com/umbraco/Announcements/issues/33)) * The Pikaday date picker, replaced by the browser's native date input ([announcement](https://github.com/umbraco/Announcements/issues/34)) * The `bootstrap3-horizontal` theme ([announcement](https://github.com/umbraco/Announcements/issues/35)) * Code marked as "Scheduled for removal in Umbraco Forms 19" Forms also follows changes in Umbraco CMS 19: * The records index uses the CMS search abstraction instead of Examine directly * Settings that offer a single choice from a dropdown use `Umb.PropertyEditorUi.Dropdown.Single` * The `@umbraco-forms/backoffice` types are generated from the CMS 19 OpenAPI document The analytics screens now draw their charts and tables with the shared Umbraco Analytics UI package. The chart, table and date range elements in `@umbraco-forms/backoffice` are removed, and some analytics Management API parameters change. For the details and upgrade steps, see the [Version Specific Upgrade Notes](/umbraco-forms/19.latest/upgrading/version-specific.md) article. #### Other * Delivery API: Return a validation error (422), instead of a 500 status code, for a file upload with invalid Base64 content * Recycle Bin: Keep folders that hold a user's or user group's start folder when emptying the recycle bin, instead of failing. A message says how many were kept. For details, see the [Recycle Bin](/umbraco-forms/19.latest/editor/managing-forms/recycle-bin.md#folders-kept-because-they-hold-a-start-folder) article * Recycle Bin: Hide the recycle bin from users with start folders * Security: Show missing and trashed start folders in the start folder picker * Security: Refuse a missing start folder when saving a user's or user group's Forms security, instead of saving part of the change --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.umbraco.com/umbraco-forms/19.latest/release-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.