coulomb/activity-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Repair production automation truth and schedule cleanup
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
Build and Publish Container Image / build-and-push (push) Successful in 18s
Details

Browse source
This commit is contained in:
tegwick 2026-08-20 11:20:23 +02:00
parent 8bcb416285
commit 944fd158de
19 changed files with 441 additions and 64 deletions
Download patch file Download diff file Expand all files Collapse all files

15
activity-definitions/weekly-sbom-staleness.md
View file

@ -1,10 +1,10 @@
---
id: weekly-sbom-staleness
name: Weekly SBOM Staleness Check
enabled: true
enabled: false
owner: custodian-agent
governance: custodian
status: active
status: paused
trigger:
type: cron
cron_expression: "0 9 * * 1"
@ -23,8 +23,15 @@ context_sources:
# Weekly SBOM Staleness Check
Runs every Monday at 09:00 Berlin time. Checks all tracked repositories for
SBOM staleness and flags any repository whose SBOM is older than 30 days.
> **Emergency-paused 2026-08-20 (ACTIVITY-WP-0031).** The 2026-08-17 fire
> emitted 75 independent rescan tasks while the bounded replacement in
> ACTIVITY-WP-0030 is blocked on CUST-WP-0062. Keep this definition disabled in
> source and production. Its deterministic weekly summary is not sufficient
> reason to retain the unbounded `for_each` task fan-out.
When enabled, this runs every Monday at 09:00 Berlin time. It checks all
tracked repositories for SBOM staleness and flags any repository whose SBOM is
older than 30 days.
ACTIVITY-WP-0021: the fleet no longer treats Forgejo issues as the primary
landing zone for automated tasks. The deterministic **state-hub-progress**