Skip to main content
Version: 2.1

Version 2.1.1 Release Notes

Release date: August 16, 2026

Version 2.1.1 is a patch release for the .NET 10 and Orchard Core 3.0 line. It keeps the Orchard Core package range at >= 3.0.0 and < 3.1.0 and the CrestApps.Core package line at stable 1.2.0. This release adds import and export support for AI tool instances and fixes the documentation search (sitemap) tool instance editor.

At a glance​

Area2.1.1 focus
AI Tool InstancesNew deployment step and recipe step for importing and exporting tool instances, with an IAIToolInstanceHandler extension point that strips credentials from exports.
Bug fixesThe documentation search (sitemap) tool instance editor now renders its Save and Cancel buttons.

New additions​

Import and export AI tool instances​

The AI Tool Instances feature can now move tool instances between tenants with the standard Orchard Core deployment and recipe pipeline.

  • Deployment step. With OrchardCore.Deployment and AI Tool Instances enabled, a new AI Tool Instances deployment step is available under Configuration → Deployment Plans. The step exports every tool instance or only the instances you select.
  • Recipe step. The deployment step emits an AIToolInstances recipe step that you can also author by hand. On import, each entry is matched by ItemId first and then by Name; a matching instance is updated in place, otherwise a new instance is created from its Source. The source must be registered on the target tenant, so enable the feature that provides it before running the recipe.
  • Recipe schema. The AIToolInstances step is now described by a recipe schema, so it is discoverable and validated when authoring recipes with the CrestApps Recipes tooling.

Credentials are stripped from exports​

Secrets are never written to an export. During export, each source can remove its own sensitive data through the new IAIToolInstanceHandler extension point. The built-in sources use it to strip their credentials:

  • The HTTP API request source clears the API key, bearer token, password, client secret, and any cached OAuth tokens.
  • The Algolia documentation search source clears the search-only API key.

After importing on the target tenant, edit the instance and re-enter the required credentials. Custom sources that store secrets can register their own IAIToolInstanceHandler to participate in this behavior.

See AI Tool Instances for details.

Bug fixes​

Documentation search (sitemap) tool instance editor​

Creating or editing a Documentation search (sitemap) tool instance did not render the Save and Cancel buttons, which made it impossible to add or update an instance from that source. The editor hint referenced a {BaseUrl} token that the localizer interpreted as a composite-format placeholder, which threw at render time and aborted the rest of the form. The hint now passes the token as a localized argument, so the editor renders completely and the buttons are available again.