CI and Release

The repository uses three primary GitHub Actions workflows.

Build

.github/workflows/build.yml restores, builds, and tests the complete product solution on Linux, Windows, and macOS. It uploads TRX test result artifacts and publishes check-run test reports when the token can create checks. A Linux NuGet pack job validates all 49 product packages and symbol packages, required NuGet metadata, generated built-in extension manifests, README badge coverage, and the two sample extension packages before uploading .nupkg and .snupkg artifacts for inspection.

Docs

.github/workflows/docs.yml builds the Lunet site from site/. Pushes to the default branch deploy to GitHub Pages. Pull requests build the site without deploying.

Release

.github/workflows/release.yml runs on valid Semantic Version v* tags and manual dispatch. It builds and tests the solution, publishes framework-dependent x64 and Arm64 app archives for Linux, Windows, and macOS, validates and packs reusable libraries and installable extensions, publishes .nupkg and .snupkg symbols to NuGet, and creates a GitHub release with generated notes and a SHA256SUMS integrity file. Releases authenticate to NuGet through trusted publishing (GitHub OIDC). The GitHub release waits for successful NuGet publication so GitHub and NuGet cannot silently diverge.

Trusted publishing setup

The repository Actions variable NUGET_USER identifies the NuGet.org username (wieslawsoltes, not an email address). Only the publish-nuget job has id-token: write permission. The pinned NuGet/login action exchanges its OIDC token for a temporary API key immediately before publishing; no stored NUGET_API_KEY secret is used.

On NuGet.org, sign in as the publishing account, open Trusted Publishing from the account menu, and create a GitHub policy with these values:

Setting Value
Policy name XamlVisualEditor
Package owner wieslawsoltes
Repository owner wieslawsoltes
Repository XamlVisualEditor
Workflow file release.yml (file name only)
Environment Leave empty; the publishing job does not use an environment
Package glob XamlVisualEditor.*
Scopes Publish new packages and new versions

See the NuGet trusted publishing documentation.

After creating the policy, run the Release workflow from a ref containing this configuration. Re-running an older failed run uses its original workflow and does not pick up the OIDC change. Trusted publishing was verified by the successful v0.2.0 release. New releases run automatically when a v* tag is pushed. The old repository API-key secret is no longer used.

Each application archive is checked for the app host, a matching runtime-specific previewer host, the VS Code compatibility host, README, changelog, and license before it is uploaded.

NuGet package metadata is centralized in Directory.Build.props: package identity defaults, author and company, repository and project URLs, MIT license, readme, icon, tags, Source Link, deterministic build settings, and symbol package output. Directory.Build.targets generates version-synchronized xve.extension.json manifests for built-in extension packages. Executable hosts and tests remain non-packable.

Local docs build

./build-docs.sh