Skip to content

v1.2.4

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 02 Nov 10:44
· 1 commit to main since this release
v1.2.4
72aad8a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Changes

Security findings with attack_evidence.status=no_evidence are no longer exported by default. unknown and suspected remain eligible for export, and SBOM inventories are unaffected.

Filtering happens before queue admission and does not count as export loss. Internal detection, local finding snapshots, span summaries, and same-request evidence upgrades remain available. no_evidence is a classification, not a safety verdict.

Configuration

To restore export of no_evidence findings, set:

BEACON_SECURITY_EXPORT_NO_EVIDENCE_ENABLED=true

The default is false. This switch controls event export to OpenTelemetry Logs and evidence JSONL.

Packages and compatibility

  • beacon-otel and beacon-profiling 1.2.4 are published on PyPI.
  • OpenTelemetry baseline: Contrib 0.66b1 / Core 1.45.1.
  • Security contract: schema v2, fingerprint v1.
  • Security runtime support: CPython 3.11–3.14.

Verification

  • Release-source CI passed Python 3.10–3.14.
  • Release workflow built and tested both distributions, then published both packages and the GitHub Release.
  • A clean CPython 3.13 environment installed both exact public PyPI versions, reported Beacon Python 1.2.4, and passed 13 export-policy, same-request upgrade, occurrence, and real OTLP HTTP receiver checks.
  • External DataKit/backend compatibility was not retested for this patch.

Rollback

Pin beacon-otel[profiling] to 1.2.3, or keep 1.2.4 and enable the configuration switch above to restore ordinary finding exports.

References

Assets 6
Loading