Skip to content

Repository CI/CD

Stable Build Reviewed 2026-09-16 purview-dev/build build-pipeline cd ci composite-action csharp devops dogfooding dotnet github-actions modular-pipelines nuget reusable-workflow

Repository CI/CD

Section titled “Repository CI/CD”

This repository dogfoods the shared Purview.Build tool: it builds and packs the tool from source, installs the generated package, then runs purview-build against itself so the project builds and packs itself.

CI (ci.yml)

Section titled “CI (ci.yml)”

Runs on pull requests and pushes to main:

  1. Check out the repository.
  2. Restore src/Build.slnx.
  3. Build gate: dotnet build src/Build.slnx --configuration Release --no-restore --warnaserror.
  4. Read and SemVer-validate the package.json version.
  5. Pack the tool from source (dotnet pack src/Build.slnx --configuration Release --no-build --output artifacts -p:Version=… -p:PackageVersion=…).
  6. Install the packed tool from the artifacts source into a temp tool path.
  7. Dogfood: run the freshly installed purview-build against this repository (with GITHUB_TOKEN). The tool restores, builds, lints, runs tests, packs, and validates itself.

Release (release.yml)

Section titled “Release (release.yml)”

Runs on push to main and is serialized by its own concurrency group (purview-build-release, cancel-in-progress: false):

  1. Read and SemVer-validate the package.json version; skip the whole job when v{version} is already tagged (the tag check makes re-merges safe).
  2. Restore and build src/Build.slnx with --warnaserror.
  3. Pack the tool from source with -p:ContinuousIntegrationBuild=true.
  4. Verify the NUGET__APIKEY secret is set.
  5. Install the packed tool.
  6. Run the release pipeline with Release__Mode=NuGet, NuGet__FeedUrl=https://api.nuget.org/v3/index.json, Release__UploadArtifacts=true, Build__RunTests=false, Build__RunLint=false, and Build__ValidatePack=true, passing GITHUB_TOKEN and NUGET_APIKEY.

The tool therefore publishes the immutable package to nuget.org and tags and releases itself (v{version} + generated-notes GitHub release with the package attached) — exactly like every other purview-dev repository. Maintainers bump the package.json version and merge; they do not create release tags manually.

GitHub package visibility

Section titled “GitHub package visibility”

GitHub initially creates NuGet packages as private. An organization owner should set the org default to Internal (Purview-Dev → Settings → Packages → Package Creation → Internal) and change any already-published package’s visibility in its Package settings → Danger Zone. See Release Flow for the exact steps and the gh api alternative.

See also

Section titled “See also”