Umbraco.Community.SchemeWeaver.Deploy
18.7.0-beta.2
dotnet add package Umbraco.Community.SchemeWeaver.Deploy --version 18.7.0-beta.2
NuGet\Install-Package Umbraco.Community.SchemeWeaver.Deploy -Version 18.7.0-beta.2
<PackageReference Include="Umbraco.Community.SchemeWeaver.Deploy" Version="18.7.0-beta.2" />
<PackageVersion Include="Umbraco.Community.SchemeWeaver.Deploy" Version="18.7.0-beta.2" />
<PackageReference Include="Umbraco.Community.SchemeWeaver.Deploy" />
paket add Umbraco.Community.SchemeWeaver.Deploy --version 18.7.0-beta.2
#r "nuget: Umbraco.Community.SchemeWeaver.Deploy, 18.7.0-beta.2"
#:package Umbraco.Community.SchemeWeaver.Deploy@18.7.0-beta.2
#addin nuget:?package=Umbraco.Community.SchemeWeaver.Deploy&version=18.7.0-beta.2&prerelease
#tool nuget:?package=Umbraco.Community.SchemeWeaver.Deploy&version=18.7.0-beta.2&prerelease
SchemeWeaver Deploy addon
Umbraco Deploy / Umbraco Cloud support for SchemeWeaver — deploy your Schema.org mappings between environments alongside the document types they belong to.
Every schema mapping is serialised to a .uda artifact in umbraco/Deploy/Revision when you save it, travels through source control with your schema, and is upserted on the target environment when a deployment is triggered. Each artifact declares a dependency on its document type, so Deploy always processes them in the right order. No more recreating mappings per environment.
This is the Deploy equivalent of the uSync addon — pick the one that matches your deployment tooling.
Requirements
- Umbraco Deploy OnPrem or Umbraco Cloud on the host site (a paid, separately installed Umbraco product — this addon does not include it). Without it, the addon logs a single startup warning and stays inactive; it never breaks your site.
Umbraco.Community.SchemeWeaverat the matching major-aligned version (installed automatically as a dependency).- Versioning follows the CMS major: install
17.xon Umbraco 17,18.xon Umbraco 18 — NuGet resolves the right build automatically.
Getting started
dotnet add package Umbraco.Community.SchemeWeaver.Deploy
That's it — the addon self-registers. Save a mapping (Settings → your document type → Schema.org tab) and a schemeweaver-mapping__{contentTypeKey}.uda file appears in umbraco/Deploy/Revision. Commit it, deploy as usual (marker file, CI/CD trigger, or the Deploy dashboard), and the mapping arrives on the target.
Behaviour worth knowing
- Deletions do not propagate. Deleting a mapping removes its
.udaat source, but the target keeps its database row until you delete it there too — the same never-delete-schema policy Deploy applies to document types. - Source overwrites target on every schema deployment, including the enabled/disabled flag. Make mapping changes at the source of your deployment flow.
- Deleting a document type automatically cleans up its mapping artifact, so stale artifacts can never fail later deployments.
- Resolver and dynamic-root configuration travel verbatim; content referenced inside them moves with Deploy's normal content workflows.
Documentation
Full documentation — behaviour, field reference, troubleshooting and a pre-release test checklist — lives in the Umbraco Deploy Integration docs.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Umbraco.Community.SchemeWeaver (>= 18.7.0-beta.2)
- Umbraco.Deploy.Infrastructure (>= 18.0.0 && < 19.0.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 18.7.0-beta.2 | 47 | 7/27/2026 |
| 18.7.0-beta.1 | 46 | 7/27/2026 |
| 17.12.0-beta.2 | 34 | 7/27/2026 |
| 17.12.0-beta.1 | 38 | 7/27/2026 |