v1.3.0
v1.3.0
-
Strict JSON/YAML config parsing: confvis now rejects unknown fields in
confidence.json / confidence.yaml configs. Typos like 'thresholdd: 80'
that previously parsed silently to 'Threshold: 0' now error out with a
message naming the unknown field. Any config carrying non-schema
metadata fields will break and needs those fields removed. -
History retention default: the new --history-max-entries flag on
'confvis gauge' defaults to 5000. Long-lived history files larger than
5000 entries will be pruned to the most recent 5000 on the next run.
Pass --history-max-entries=-1 or 0 to restore unbounded behavior. -
feat(history): cap history growth via Prune/PruneRef helpers + new
--history-max-entries flag, covering both file-backed and git-ref-
backed history storage. -
fix(confidence): Report now accepts the documented Passed/Baseline/
Delta emit-json output fields on input, so 'confvis aggregate
--emit-json ... | confvis baseline save' round-trips cleanly. -
fix(checks): escape markdown metacharacters (|, newline, backtick) in
the GitHub Checks summary so report titles/factor names with
punctuation no longer break the rendered table. -
fix(deps): bump Go toolchain to 1.26.2 to pick up stdlib security
fixes (5 callable CVEs in crypto/tls, crypto/x509, html/template). -
chore(infra): pin docker-compose SonarQube image by sha256 digest.
-
test(trufflehog): cover Source.Fetch via mock bash script (package
coverage 60.9% -> 92.8%). -
internal/confidence.Report.Passed() renamed to IsPass() to free the
Passed field name for the documented JSON output shape. Not a public
API break (internal/ package).