v7.0.24
GitGuardex v7.0.24
Changes since v7.0.23.
v7.0.24
- Bumped
@imdeadpool/guardexfrom7.0.23to7.0.24so GitHub Releases and the npm publish retry can advance together afterv7.0.23landed on GitHub but not on npm. - Release verification no longer loses its base ref on tag-triggered runs, so the publish workflow keeps the history it needs before packing and publish checks.
- Keep the release scoped to version and release automation metadata only; the packaged Guardex CLI payload stays aligned with the already-verified
mainbranch contents.