Run CI-equivalent checks

Map local validation to pull-request, main, nightly, and release workflow lanes.

Updated 6 September 2026 · 2 min read

Pull-request CI routes checks by changed path and risk. Nightly and release workflows broaden compatibility, lifecycle, provenance, and reproducibility coverage.

verify

Run the local pull-request baseline

devenv test
devenv tasks run operator:bootstrap
devenv tasks run operator:doctor
devenv tasks run operator:ci-core

The advisory Devenv Contract job runs on toolchain changes and pushes to main. It proves that the pinned base and editor-profile shells can be constructed on the CI runner and that their version contracts pass. Base and editor duration and closure measurements remain separate. The job pulls from the public project and Devenv caches. It publishes newly built paths to the project cache only from pushes to main when the repository has a per-cache CACHIX_AUTH_TOKEN; pull requests are always read-only. The existing required jobs remain the merge authority while the project migrates their setup steps incrementally.

CI concernLocal entry point
Pinned environment contractdevenv test
Core quality gatesdevenv tasks run operator:ci-core
API inventory and released CRD compatibilitymake verify-api-contract
Hugo documentation and redirectsmake docs-build
Vendored dependencies and licensesmake verify-vendor, make license-check
Static and filesystem securitymake semgrep-ci, make security-ci
Focused cluster behaviormake test-e2e-ci, make helm-e2e-smoke
Prior-stable operator upgrademake test-e2e-operator-upgrade
Existing platform clustermake test-e2e-existing

Docs-only changes normally avoid broad cluster E2E. Backup, upgrade, security, provisioner, admission, controller-critical, or seal-path changes expand into targeted shards. Maintainers can request the full E2E set with the repository’s CI label.

The required API Contract job rejects unclassified API fields, stale inventory snapshots, and breaking or review-required schema changes against the released 0.5.0 CRDs. It runs for contract-related changes, pushes to main, and manual CI runs. Release validation runs the same gate before image builds and publication. make report-crd-compatibility produces a diagnostic report without weakening the required gate.

The E2E manifest owns suite routing, isolation, parallelism, and supported test versions. Do not duplicate those values in workflow logic. Run make e2e-ci-matrix or the nightly matrix commands before changing routing.

Continue with supply-chain controls and release management.

Search the handbook

Try “install”, “threat model”, or “compatibility”.