chore(deps): force dependency graph re-parse to clear 11 stale Dependabot alerts - #159
Merged
Merged
Conversation
…re-parse 11 Dependabot alerts stayed open after #157 against dependency graph entries that do not exist anywhere in the repo. The current SBOM still lists keras 3.13.2, python-multipart 0.0.27, tensorflow 2.20.0, numpy 2.4.2 and fastapi 0.133.1 alongside the correct current versions, all attributed to requirements.txt: - 4 python-multipart alerts recorded "== 0.0.27" (the repo pinned 0.0.32 for months before this work removed the dependency entirely). - 7 keras alerts were newly created against "== 3.13.2"; requirements-ml.txt pins 3.15.1 and nothing in the tree references 3.13.2. Touching both manifests should make GitHub re-parse them and drop the stale records. The comments themselves are useful either way: they point at the generated hash-pinned lock files added in #157. Verified unchanged: pinned versions are identical, only comments were added.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
After #157 and #158, 11 Dependabot alerts remain open against dependency graph entries that do not exist anywhere in the repository. This PR touches both pip manifests to force GitHub to re-parse them.
The stale records
The current SBOM (
GET /dependency-graph/sbom, generated 02:36 UTC today) lists both the correct new versions and obsolete ones:keraspython-multiparttensorflownumpyfastapiscikit-learnredisThe 11 open alerts all trace to those stale rows, all attributed to
requirements.txt:python-multipart) record== 0.0.27. The repo pinned0.0.32for months before fix: clear all 17 Dependabot alerts and 22 SonarCloud issues, update deps to latest #157 removed the dependency, so these were already stale before this work started — which is why bumping to the latest release never closed them.keras) were created 02:19 UTC against== 3.13.2.requirements-ml.txtpins3.15.1, andgrepfinds no3.13.2anywhere in the tree.For contrast, the alerts on manifests GitHub re-parsed normally did close: the 6 original keras alerts on
requirements-ml.txtand all 7 npm alerts onclient/package-lock.jsonwent away on merge (17 → 11).Changes
Comment headers added to
requirements.txtandrequirements-ml.txtpointing at their generated hash-pinned counterparts from #157. No version pin is changed — the diff is comments only.The intent is to change the manifest blobs so GitHub re-parses them and drops the stale rows.
Testing
pytest -q— 34 passedgit diffconfirms only comment lines added; every==pin is byte-identicalIf this does not clear them
Then the rows are held by an orphaned dependency-submission snapshot rather than native parsing, and they cannot be cleared from the repo side. In that case the 11 alerts need dismissing in the Security tab as "no longer used" — they are phantom records, not live vulnerabilities. Worth confirming from the manifests themselves:
requirements.txtcontains nopython-multipart, andkerasis pinned to3.15.1, which is patched for all six advisories.I could not verify or dismiss these via the API: the available token lacks the
security_eventsscope, soGET /dependabot/alertsreturns 404 and dismissal is not possible programmatically. Alert state above was read through the GraphQLvulnerabilityAlertsconnection, which only permits reads.