41 Pillow Dependabot alerts remain open after graph and updater confirm 13.0.0 #211736
Replies: 3 comments
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
This comment was marked as low quality.
This comment was marked as low quality.
|
Hi, You've already ruled out the usual client-side causes. The graph, SBOM and updater all agree on Pillow 13.0.0, so what is left is persisted alert state that isn't being reconciled. That is a GitHub-side problem, and community members can't reprocess it. Here is what I would still check, and then how to escalate. 1. Look for other manifests or lockfiles that still resolve to an old Pillow Dependabot closes an alert only when no manifest in the repository, on the default branch, still resolves a vulnerable version. Check for: git ls-files | grep -Ei "requirements|Pipfile|poetry.lock|pyproject|setup.py|setup.cfg|constraints"
git grep -n -i "pillow" -- . ':!*.md'Include submodules, vendored folders, and any 2. Check whether the alerts are tied to a different ecosystem or path Open one alert and confirm its manifest path and ecosystem match 3. Request reprocessing through GitHub Support, not Discussions Staff can't inspect alert-evaluation queues from a discussion thread. Open a ticket at https://support.github.com/contact (Code security / Dependabot) and include:
A concise table of timestamps and run IDs helps support route it to the right team. 4. Optional low-risk nudges that don't rewrite history
5. What to avoid Don't dismiss the alerts as a workaround. Dismissal records a different state from "fixed" and can't be undone cleanly in the history you want to preserve. After 24 hours or more without change, support is the supported path. I'd also mention in the ticket that the GitHub Community discussion exists, so they can link the reports. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Dependabot
Discussion Details
Repository: https://github.com/senyo888/codex-pets (public)
Please investigate and reconcile the 41 Dependabot alerts. They still report requirements-dev.txt with = 12.3.0, although the committed manifest and current GitHub dependency graph report Pillow 13.0.0. Please preserve the alert history and mark genuinely remediated alerts fixed through normal server-side evaluation, without dismissing them.
Evidence:
Attempts:
Please inspect the alert-evaluation/reconciliation state after these accepted submissions and reprocess it if stuck. The graph and updater agree the dependency is patched; the discrepancy is persisted alert state. The internal queue and exact backend cause are not exposed through public interfaces. Please explain the cause if available and restore normal closure without suppression, disabling monitoring, or rewriting the dependency inventory.
Latest verification: at 2026-10-31 13:03:26 UTC, the paginated REST API still reported 41 open alerts, zero fixed timestamps, and zero dismissals.
Is there another supported way to request alert reconciliation, or can the GitHub team investigate the accepted submissions above? The documented refresh has already succeeded twice. I want these alerts closed as fixed after evaluation, not dismissed or hidden.
All reactions