You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@magpie.apache.org by "potiuk (via GitHub)" <gi...@apache.org> on 2026/07/07 13:11:10 UTC
[PR] refactor(skills): push regenerated CVE JSON on every regen, not only at fix-released [magpie]
potiuk opened a new pull request, #774:
URL: https://github.com/apache/magpie/pull/774
## Summary
- Step 5b of `security-issue-sync` now states explicitly that the CVE-tool
push fires on **every** regen of the CVE JSON, not only at the
`pr merged → fix released` transition.
- Enumerates the non-fix-released triggers (advisory-URL/`announced`
close-out on PUBLISHED records; reviewer-feedback title/summary edits on
DRAFT/REVIEW; field corrections).
- Reframes the `fix released` paragraph as the one instance of the general
rule that is *also* mandatory/non-deferrable.
- Documents that a generator-driven `REVIEW → DRAFT` state walk-back on a
title/summary edit is intended.
## Motivation
Step 5b's push mechanics are already trigger-agnostic, but the only
*emphatic* prose about when the push fires is the `fix released`
"not deferrable" paragraph. In a real Apache Airflow sync run that
prominence led the operator to hedge and *not* auto-push six advisory
close-out regens (adding the `vendor-advisory` reference to already-PUBLISHED
records) plus a reviewer-feedback title/summary edit — the records drifted
from the tracker body until a manual re-push. This removes the ambiguity.
Originated as a local adopter override:
`.apache-magpie-overrides/security-issue-sync.md` ("Always push the
regenerated CVE JSON on every regen").
## Migration path for existing adopters
Documentation-only clarification of existing behaviour — no config knob, no
default flip. Adopters running the authenticated-session push path get the
same mechanics; those without a session still fall through to the
manual-paste hand-off exactly as before. All Step 5b guardrails (pre-push
hygiene gates, session probe, verify-after-push) are unchanged.
## Test plan
- `SKIP=lychee prek run --files skills/security-issue-sync/apply-and-push.md`
→ all hooks pass (markdownlint, typos, check-placeholders,
skill-and-tool-validate).
- Exercised end-to-end in the originating adopter: seven records
regenerated + pushed (six PUBLISHED gaining the vendor-advisory reference,
one walked REVIEW→DRAFT on a title/summary edit), states verified via
`vulnogram-api-record-fetch --state-only`.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] refactor(skills): push regenerated CVE JSON on every regen, not only at fix-released [magpie]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk merged PR #774:
URL: https://github.com/apache/magpie/pull/774
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org