Skip to main content
Version: 2.1

Version 2.1.2 Release Notes

Release date: August 18, 2026

Version 2.1.2 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 fixes two defects: agent skills were missing from published MCP Server sites, and the AI email tool sent messages with the logged-in user as the sender.

At a glance

Area2.1.2 focus
MCP ServerAgent skills are now included when you publish a site that installs the module from NuGet, so the server exposes skill prompts and resources.
AI AgentThe Send Emails tool no longer writes the logged-in user into the From, Sender, or Reply-To headers.
MCP Server settingsThe None authentication option is now labeled None (Anonymous access).

Bug fixes

Agent skills are missing from published MCP Server sites

A site that installed CrestApps.OrchardCore.AI.Mcp from NuGet published without any agent skills. The MCP server started correctly and exposed the selected tools, but ListResources and ListPrompts returned no skills. The problem did not occur during local development, which made it difficult to find.

The cause was the packaging format of the CrestApps.AgentSkills.Mcp.OrchardCore dependency. Up to version 1.1.0, that package shipped the skills as NuGet contentFiles. NuGet applies contentFiles only to direct package references and to project-reference chains. NuGet removes them when the package arrives through another package, which is a transitive package reference. Local development uses project references and therefore worked, but a published site references the module as a package and received no skill files. The runtime loader then found an empty .agents/skills directory and registered nothing.

This release updates the dependency to CrestApps.AgentSkills.Mcp.OrchardCore 1.1.1. That version ships the skills under skills/ together with a buildTransitive MSBuild targets file. Assets in buildTransitive flow through transitive package references, so the skills are copied to the build output and the publish output at .agents/skills/ for every consumer, at any depth in the dependency graph.

No configuration change is required. Update to 2.1.2, publish the site again, and the MCP server exposes the skills as prompts and resources.

note

If your application supplies its own skills directory, you can prevent the packaged skills from being copied. Set the IncludeCrestAppsAgentSkills MSBuild property to false in your project.

The AI email tool used the logged-in user as the sender

The Send Emails tool wrote the address of the logged-in user into the From, Sender, and Reply-To headers of the message. Mail providers that only permit approved sender addresses rejected these messages, and the behavior let an email appear to come from a user who did not send it.

The tool now leaves these headers empty and lets the configured email provider apply the tenant default sender. If a provider has no sender configured, it fails with a configuration error instead of falling back to the logged-in user.

The tool description also changed from Sends a email message on the behalf of the logged user to Sends an email using the configured email provider, which describes the corrected behavior.

Improvements

Clearer MCP Server authentication label

In Settings → Artificial Intelligence → MCP Server, the authentication option named None (development only) is now named None (Anonymous access). The option is unchanged. The new label describes what the option does, because some deployments intentionally expose an anonymous MCP endpoint.