EnvGuard v0.6.6 — Organization Policy Schema Fix & Multi-Repo Scan Stability
What's Changed in EnvGuard v0.6.6
EnvGuard v0.6.6 is a patch release fixing two critical issues in the v0.6.x organization policy and multi-repository scanning workflows:
1. Organization Policy locked_disabled_rules Schema Alignment (Bug A)
- Fixes False-Positive Warnings: Fixed a validator/schema mismatch where defining
locked_disabled_rulesin.envguard-org.ymltriggered an erroneous"Unknown top-level key"warning. - Diagnostics & Status Consistency:
envguard doctor(Check 5b) andenvguard statusnow recognizelocked_disabled_rulesas a first-class schema field, reportingPASSandACTIVEwithout spurious warnings. - Strict Schema Enforcement: Validates that
locked_disabled_rulesis a list of rule IDs and integrates them into the composite policy floor.
2. Multi-Repository Scan Stability Fix (Bug B)
- Fixes Scan Crash with Findings: Fixed a
TypeError(print_scan_findings() got an unexpected keyword argument 'files_scanned') that crashedenvguard scan --reposin default text output mode whenever any scanned repository contained active findings. - Unified Findings Presentation: Multi-repo scans now cleanly display both the high-level repository summary table and the detailed secret findings table across all repositories.
Verification
- Automated Tests: 169 passed (
pytest tests/). - 100% Local: Zero network telemetry, zero cloud backends.