v7.0.21
GitGuardex v7.0.21
Changes since v7.0.20.
v7.0.21
- Bumped
@imdeadpool/guardexfrom7.0.20to7.0.21so npm can publish the next release from the current merged mainline. - Keep the release scoped to version and release metadata only; the package payload stays the same as the verified
mainbranch contents. - Published-release automation will pick up this new package version once the matching GitHub release is created.