argoyleandrenovate
7c0445b4ef
Unbound Release / Check Preconditions (push) Successful in 24s
Unbound Release / Create Tag (push) Skipped
Unbound Release / Generate Changelog and Handle PR (push) Successful in 41s
Unbound Release / Create Release (push) Successful in 42s
Release / release (push) Successful in 1m50s
cron-checker / build (push) Successful in 13m47s
cron-checker / test (push) Successful in 1m8s
cron-checker / vulnerabilities (push) Successful in 55s
Root cause of the failing `vulnerabilities` and `test` jobs on the open Renovate PRs. `actions/setup-go` resolves `go-version: stable` from the `actions/go-versions` manifest. On 2026-08-14 that manifest still pointed at **go1.26.5**, which carries 4 stdlib vulnerabilities (GO-2026-6218, GO-2026-6090, GO-2026-5972, GO-2026-5026), so `govulncheck` failed. It also broke the `test` job on #396 once go.mod required `go >= 1.26.6`, since setup-go sets `GOTOOLCHAIN=local`. Switching to `go-version-file: go.mod` makes CI install exactly the toolchain go.mod declares. Renovate already tracks that directive (#395), so the Go version stops depending on manifest publishing lag. After this lands, #394 / #395 / #396 should be rebased and re-run. --------- Co-authored-by: Renovate Bot <renovate@unbound.se> Reviewed-on: #397
cron-checker
A small container which periodically (every 60s) checks for a cronjobs which are not running according to schedule and sends a notification to Slack.