[github-actions]

🤖 Automated bundled-toolchain refresh

The prebuilt Caddy/CrowdSec toolchain image was rebuilt (daily
--no-cache --pull, or a tracked-pin change) and produced a new
digest.

	Tag	Digest
Old	caddy-crowdsec-9eb9862f44b9e769	sha256:b41e571d5951bbfc3daa3dccdca033ad9dee535a8e720ac7e3b0bce338f223b2
New	caddy-crowdsec-1efe7f19fa52a512	sha256:6575f4c6a9f76074870c64df9dd4c9ebee812342f37f52ae5ef8f511ba9f8f00

The Trivy CRITICAL/HIGH gate on the new image passed on the rebuild
run. Merging updates the shipped Caddy/CrowdSec binaries.

Verification

• CI green (verify-toolchain-pin, Docker Build, integration)
• Trivy diff on the final app image shows no new CRITICAL/HIGH

Auto-generated by .github/workflows/toolchain-image.yml.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[github-actions]

✅ Supply Chain Verification Results

✅ PASSED

📦 SBOM Summary

• Components: 1769

🔍 Vulnerability Scan

Severity	Count
🔴 Critical	0
🟠 High	0
🟡 Medium	0
🟢 Low	0
Total	0

📎 Artifacts

• SBOM (CycloneDX JSON) and Grype results available in workflow artifacts

---

_{Generated by Supply Chain Verification workflow • View Details}

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.