Repository navigation
CI/CD integration: nlsc ci command and lockfile enforcement #149
Description
Problem
Teams need automation-native tooling. There is no nlsc ci command, no strict lockfile enforcement mode, and no reproducible build guarantees for CI environments.
Acceptance Criteria
-
nlsc cicommand: non-interactive, strict mode, exits non-zero on any warning -
--frozen-lockfileflag: fails if lockfile is out of date -
nlsc build --reproducible: deterministic output with hash verification - GitHub Actions example in docs
- Exit codes documented and stable
Why This Blocks v1.0
Engineering teams won't bet a project on a toolchain that isn't CI-native.
Activity