> 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-automate/19.latest/release-notes.md).

# Release Notes

Get an overview of the things changed and fixed in each version of Umbraco Automate.

This section summarizes the changes to Umbraco Automate released in each version. Each version links to the full list of changes on GitHub, and individual items link to the pull request that made the change. The complete history is in the [Umbraco Automate changelog](https://github.com/umbraco/Umbraco.Automate/blob/v19/main/Umbraco.Automate/CHANGELOG.md).

If there are any breaking changes or other issues to be aware of when upgrading, they are also noted here.

## Release History

This section contains the release notes for Umbraco Automate 19, including all changes for this version.

### [19.0.0-rc1](https://github.com/umbraco/Umbraco.Automate/compare/Umbraco.Automate@18.5.1...Umbraco.Automate@19.0.0-rc1) (November 13th 2026)

The first release of Umbraco Automate for Umbraco CMS 19. It includes everything in Umbraco Automate 18.6.0, and the changes below. Umbraco Automate 19 needs Umbraco CMS 19.0.0-rc1 or later and .NET 11 [#502](https://github.com/umbraco/Umbraco.Automate/pull/502).

{% hint style="warning" %}
This release changes some existing behavior. Review these points before upgrading:

* **Find Content and Find Media use Umbraco Search.** Only the item name is searched. **Contains** no longer finds text in the middle of a word, so `press` doesn't find "Compress Archive". **Exact** matches the whole name, so `homepage` no longer finds "The Homepage". A search examines at most 2000 results, and items in the recycle bin are left out [#502](https://github.com/umbraco/Umbraco.Automate/pull/502). For more information, see [Find Content and Find Media](/umbraco-automate/19.latest/concepts/actions.md#find-content-and-find-media).
* **Publishing shared properties needs a permission.** On content that varies by culture, **Publish Content** only publishes shared properties when one of the service account's groups has **Allow editing shared content**. Without it, the step succeeds and writes a warning to its log [#502](https://github.com/umbraco/Umbraco.Automate/pull/502). For more information, see [Publishing Shared Properties](/umbraco-automate/19.latest/concepts/workspaces.md#publishing-shared-properties).
* **Some pickers must have a value.** **Create Content**, **Create Media**, **Move Content**, and **Move Media** steps with an empty required picker fail validation when you publish the automation [#502](https://github.com/umbraco/Umbraco.Automate/pull/502).
  {% endhint %}

#### Removed configuration

`Umbraco:Automate:Enabled`, the `Umbraco:Automate:Governance` section, and `Umbraco:Automate:Scripting:StatementTimeout` are removed. They had no effect, so sites that still set them work the same [#502](https://github.com/umbraco/Umbraco.Automate/pull/502). For more information, see [Configuration](/umbraco-automate/19.latest/getting-started/configuration.md).

#### Breaking changes for extensions

These changes affect custom code that builds on Umbraco Automate:

* Custom implementations of these interfaces must implement members that had a default implementation before [#502](https://github.com/umbraco/Umbraco.Automate/pull/502), [#590](https://github.com/umbraco/Umbraco.Automate/pull/590):
  * `IAutomationRunService`: `GetStepRunDataAsync` and `GetTriggerDataAsync`.
  * `IAutomationActionAuthorizer`: `AuthorizeContentRootAsync`, `AuthorizeMediaRootAsync`, `AuthorizeContentParentAsync`, `AuthorizeMediaParentAsync`, and the Library element members.
  * `IOAuthCredentialsService`: `GetCredentialIdsNotModifiedSinceAsync`.
  * `IContentValueNormaliser`: `NormaliseProperties` and `ReadProperty` for `IPublishedElement`.
* Removed: the `NotifyEditorAction` constructor without an `IAutomationActionAuthorizer`, the `CatalogueMapDefinition` constructor without a logger, `AutomateOptions.Enabled`, `GovernanceOptions`, `ScriptingOptions.StatementTimeout`, and `ScriptExecutorOptions.StatementTimeout` [#502](https://github.com/umbraco/Umbraco.Automate/pull/502), [#590](https://github.com/umbraco/Umbraco.Automate/pull/590).
* Constructors changed: `PublishContentAction` takes `IUserService` and `PropertyEditorCollection`. `FindContentAction` and `FindMediaAction` take `ISearcherResolver` and `IEntityService` instead of `IExamineManager`, and `FindContentAction` also takes `ILanguageService` [#502](https://github.com/umbraco/Umbraco.Automate/pull/502).
* Dropdown settings use the `Umb.PropertyEditorUi.Dropdown.Single` editor, because `Umb.PropertyEditorUi.Dropdown` is always multi-select in Umbraco 19. The stored value doesn't change. Update dropdown settings in your own actions and triggers the same way [#502](https://github.com/umbraco/Umbraco.Automate/pull/502).


---

# 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-automate/19.latest/release-notes.md?ask=<question>&goal=<user_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.
