Skip to content
Purview Dev logo

Migration: aspire-resourcekit

Stable Build Reviewed 2026-11-02 purview-dev/build Star on GitHub 1 build-pipeline cd ci composite-action csharp devops dogfooding dotnet github-actions modular-pipelines nuget reusable-workflow

This repository currently contains a vendored copy of build/PipelineCLI. Migrate it as follows.

  1. Replace the vendored build/PipelineCLI with the shared Purview.Build tool pinned to the chosen released version.
  2. Add this purview-build.json:
{
"Build": {
"Solution": "src/ResourceKit.slnx",
"TestRoot": "src/tests",
"TestPatterns": "*Tests.csproj",
"TestFilter": "/*/*/*/*[Category=Unit]"
},
"Release": { "Mode": "None" }
}
  1. Replace pr.yml and release.yml with thin callers of purview-dev/build/.github/workflows/purview-build.yml and purview-dev/build/actions/purview-release (the release entry point is a composite action), passing build-version. Keep the [Category=Unit] filter in the release caller.
  2. In the release caller set release-mode: NuGet, grant id-token: write, and pass trusted-publishing: true plus nuget-user; no stored NuGet key is involved.
  3. Run the PR pipeline, then delete build/PipelineCLI and its pipeline-only central package declarations (ModularPipelines*, NuGet.Packaging/Versioning).

The old solution path and unit-test filter are preserved exactly. Other repositories migrate by changing only the JSON paths/patterns; for example build-sdk can list unit and integration project globs in Build:TestPatterns.