Skip to content

v1.3.0

Choose a tag to compare

View all tags
@rennf93 rennf93 released this 01 Oct 20:38
· 9 commits to master since this release
v1.3.0
This tag was signed with the committer’s verified signature.
rennf93 Renzo F
GPG key ID: B48363D3A3A4CF78
Verified
Learn about vigilant mode.
88382e5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v1.3.0 (2026-10-01)

guard-core-go v4.3.0 floor (the corpus-parity engine)

Changed

  • Raised the engine floor to github.com/rennf93/guard-core-go/v4 v4.3.0, the corpus-parity release. The v4.3.0 engine is validated against the full conformance corpus: the pattern_safety, events and redis_interop suite kinds now run against the real engine alongside detect and pipeline (fail-closed baselines), the spec 12 observable event stream is ported (security event bus, metrics collector, dynamic-rules agent pipeline, the emission fidelity wave that closes the events surface to reference parity at 32 of 38 cases), plus the detection performance monitor, the security-headers Redis cache with the cross-worker sync contract, and the manager-level geo country verdict (GeoIPManager.CheckCountryAccess). Everything flows to the adapter through the unchanged middleware surface: agent integrations receive the new event stream via the existing handler hooks, and the engine-level changes require no adapter code. The module's go directive follows the engine to 1.26.0 (the engine's toolchain floor), and the CI matrix (ci.yml and release.yml), the example-app smoke images and the Makefile's GO_IMAGE move to go 1.26 with it, mirroring the engine's own go 1.26 floor wave (guard-core-go #36).
  • Dependency bumps: the codeql-action suite to 4.38.2 (#17, #18) and golang.org/x/text v0.41.0 to v0.42.0 via the engine module graph.

Added

  • A hard 100% coverage gate wired into CI (#22): the adapter surface is fully covered (coverage_test.go drives the shim and middleware paths the pipeline exercises), and the gate (check_coverage.sh) fails closed on a missing or empty profile and refuses anything under 100% total.
  • staticcheck joins the CI gates (#21) with the findings fixed ahead of the gate.
  • The upstream-drift suite runs on go 1.26 (#20) to match engine master's toolchain floor.
  • The guard-core process baseline (#21): hygiene files (SECURITY, CONTRIBUTING, Code of Conduct, funding, issue and PR templates), dependabot, the labeler and scheduled lint.
Assets 2
Loading