kit 1.29.0
Added
[scan] guarddog = true— persistent project opt-in for the local malware scan. GuardDog (#105) was enabled only via the ephemeralKIT_GUARDDOG=1env var.kit checknow also honors aguarddog = trueflag under[scan]in.kit.toml(best-effort config read; env var still works and takes precedence in spirit — either enables it). So the choice lives in committed project config, not a per-shell env var. The skip message points at both. (Foundation for an interactivekit setupprompt to write the flag — a follow-up.)
Full changelog: https://github.com/sandstream/kit/blob/v1.29.0/CHANGELOG.md
Verify this release:
git tag -v v1.29.0
npm audit signatures