The GitHub Actions job "prek" on airflow-steward.git/oauth-cve-auto-push has failed. Run started by GitHub user potiuk (triggered by potiuk).
Head commit for run: 5a949c01d7ff19e57e09a80d577264b569b4574c / Jarek Potiuk <[email protected]> feat(security-issue-sync): auto-push CVE JSON via Vulnogram OAuth API at sync time When the operator's machine has a valid Vulnogram OAuth session configured (the one-time `vulnogram-api-setup` per machine), `security-issue-sync` now pushes the regenerated CVE JSON to the record directly via `vulnogram-api-record-update` immediately after Step 5a's regen. The push is mechanical and follows from the same JSON the user just approved as part of the body update; no separate confirmation prompt. State-machine transitions (`DRAFT` → `REVIEW` → `READY` → `PUBLIC`) stay with the release manager because they include the CNA-feed dispatch trigger. Three outcomes from `vulnogram-api-check`: - `valid` → push runs; on success the timestamp is recorded and the release-manager hand-off comment is rendered from the new OAuth-pushed variant template (RM verifies + does the UI state-transition clicks, no paste step). - `expired` → push skipped, manual-paste hand-off applies; the recap nudges the operator to re-run `vulnogram-api-setup`. - `not-configured` → push skipped silently; today's manual-paste hand-off applies. New templates carry the same v1 marker as the manual-paste variants, so idempotency detection is unchanged. The Step 4 apply mechanic now flips into PATCH-edit-in-place mode when the marker is found and the existing body's variant differs from the variant the current sync would render — the comment URL, timeline position, and prior notifications survive the variant flip. Same PATCH-don't-post rationale as the rollup-comment upsert: a fresh duplicate comment buries the timeline. Generated-by: Claude Code (Opus 4.7) Report URL: https://github.com/apache/airflow-steward/actions/runs/25709404294 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
