Pull requests and merges to master run CI and Release (.github/workflows/ci.yml):
npm run lint:cssnpm run validate:contractsnpm run validate:manifestdotnet build src/dotnet/AspFrontend.csproj -c Releasedotnet test src/dotnet/tests/AspFrontend.Tests/AspFrontend.Tests.csproj -c Release --no-buildnpm run test:unitnpm run test:componentnpm run buildRun the full local quality bar with npm run lint (CSS, JS, contracts, manifest) and dotnet test src/dotnet/tests/AspFrontend.Tests/AspFrontend.Tests.csproj -c Release.
Commits with messages starting release: skip the build job to avoid duplicate runs after semantic-release pushes the version bump.
master only)Merges to master also trigger semantic-release, which:
@policedigitalservices/asp-frontend to GitHub Packages (npm)AspFrontend to GitHub Packages (NuGet)package.json, composer.json, and src/dotnet/Directory.Build.propsRelease commits are written as release: <version>.
Azure Pipelines is configured in azure-pipelines.yml.
CI runs automatically on master. Other branches can be built manually (queue the pipeline and select the branch).
The Azure build number is derived from package.json:
master — the package version as-is (e.g. 2.17.0)2.17.0-side-nav.12345), so test releases do not collide with the real versionazure-pipelines.yml)npm cinpm run test:unitnpm run builddist/ as a build artefactnpm run test:axe is available locally and can be added to CI later. It may produce incomplete results for some rules (particularly colour contrast). See docs/accessibility-testing.md for known issues and troubleshooting.Imported from docs/ci.md in asp-frontend.