You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@magpie.apache.org by po...@apache.org on 2026/07/11 15:49:16 UTC

(magpie) branch main updated: fix(security-issue-sync): read the fix-release signal authoritatively; warn against summarized-fetch false negatives (#820)

This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/magpie.git


The following commit(s) were added to refs/heads/main by this push:
     new 06a9c767 fix(security-issue-sync): read the fix-release signal authoritatively; warn against summarized-fetch false negatives (#820)
06a9c767 is described below

commit 06a9c767372942888c0b52d44fd7b0ed551df9cc
Author: Jarek Potiuk <ja...@potiuk.com>
AuthorDate: Sat Jul 11 17:49:11 2026 +0200

    fix(security-issue-sync): read the fix-release signal authoritatively; warn against summarized-fetch false negatives (#820)
    
    The "a release carrying the fix has shipped" detection row delegated the
    per-scope recipe to project config but gave no guidance on reading the
    signal reliably. Add a vendor-neutral caution: determine release-shipped
    from the project's release announcement ([ANNOUNCE] / registry feed) plus,
    where available, the package changelog naming the fix PR and the
    git-ancestry of the fix commit under the release tag. Do NOT infer release
    state from a prose-summarizing fetch of a large package-index JSON API -- a
    WebFetch-style summary can silently mangle the version / upload-date and
    report a false "not released", which strands a shippable advisory at
    pr merged with no RM hand-off. A false negative is the dangerous direction,
    so trust the announcement + changelog over any summarized fetch.
    
    Generated-by: Claude Code (Claude Opus 4.8)
---
 skills/security-issue-sync/gather.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/skills/security-issue-sync/gather.md b/skills/security-issue-sync/gather.md
index 03436f79..711df3eb 100644
--- a/skills/security-issue-sync/gather.md
+++ b/skills/security-issue-sync/gather.md
@@ -349,7 +349,7 @@ update, label change, or next-step recommendation in Step 2:
 | The *"CWE"* body field is populated with a bare `CWE-NNN` token (no description text) — e.g. `CWE-22` or `CWE-502` alone, without the canonical short description that follows in the format `CWE-NNN: <Title>` | Propose expanding the field to `CWE-NNN: <Canonical Title>` per the MITRE CWE catalog (e.g. `CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')`, `CWE-502: Deserialization of Untrusted Data`, `CWE-601: URL Redirection to Untrusted Site ('Open R [...]
 | The tracker's *Security mailing list thread* body field references a **private scanner product** (declared in [`<project-config>/scanner-products.md`](../../<project-config>/scanner-products.md) — e.g. internal SAST, partner-shared scan, unpublished bug-bounty pipeline) **AND** the *Reporter credited as* body field names a person rather than `anonymous` / a public handle, **AND** there is no signal the finder consented to public credit (no inbound `security@` message from them under th [...]
 | The **issue title** contains adopter-specific or internal noise that would otherwise ship to the public CVE record — leading or trailing project-name tokens (e.g. ``<vendor> <product>:`` / ``in <vendor> <product>`` / ``(<vendor> <product> X.Y)``), internal split markers (``(split from #NNN)`` / ``(split for scope clarity from #NNN)``), report-form classifiers (``[ Security Report ]`` / ``[Security Issue]``), external-tracker IDs in parentheses or brackets (``[GHSA-xxxx-xxxx-xxxx]``, `` [...]
-| A release carrying the fix has shipped. Detection is **scope-dependent** — different scope labels on a project can ride different release trains, each with its own *"is it released?"* signal (which artifact registry to consult, what to query, how to map a tracker's milestone to that registry, partial-release edge cases). The per-scope detection recipe lives in [`<project-config>/scope-labels.md` — *Detecting that a fix release has shipped*](../../<project-config>/scope-labels.md#detect [...]
+| A release carrying the fix has shipped. Detection is **scope-dependent** — different scope labels on a project can ride different release trains, each with its own *"is it released?"* signal (which artifact registry to consult, what to query, how to map a tracker's milestone to that registry, partial-release edge cases). The per-scope detection recipe lives in [`<project-config>/scope-labels.md` — *Detecting that a fix release has shipped*](../../<project-config>/scope-labels.md#detect [...]
 | GHSA state transition (opened, accepted, published, rejected) in a GHSA-forwarded email | If the GHSA is closed as "not accepted" but the security team accepted the report on `security@`, flag the divergence in the status comment so it is not lost. |
 | Team member saying *"let's also backport to v3-2-test"* / *"please mark X for backport"* | Note the requested backport label on the public PR as an item for Step 9 of the `security-issue-fix` workflow. |
 | Reporter flagging a second distinct vulnerability on the same thread | Surface as an explicit question to the user — it may warrant a separate tracking issue. |