Dependabot fixes not clearing

[pachewise]

🏷️ Discussion Type

Bug

Body

Dependabot alerts on my repo (https://github.com/pachewise/pachewise.github.io) are not clearing even though I am merging the relevant dependabot PRs. When I go to the Security tab, I see "all" the alerts I have had in the past month or so; when I click on them, there is either a "creating a security update" (only for picomatch, which I was alerted to today and have already merged the PR), or "No Security Update Needed" (but the alert won't go away).

See screenshots below. Is this a new behavior change or a bug?

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[Sagargupta16]

This is a common issue with Dependabot alerts. Merging the PR doesn't always auto-dismiss the alert. A few things to check:

1. Lock file might not be updated - If you're using npm/yarn, merging a Dependabot PR updates package.json but sometimes the lock file still references the old version. Run npm install or yarn install locally, commit the updated lock file, and push.

2. Transitive dependency - The vulnerable package might be a sub-dependency. Dependabot updates the direct dep, but the transitive dep might still pull in the old version. Check with:

   npm ls <vulnerable-package>

   If it shows the old version under another package, you need that parent package updated too.

3. Force re-evaluation - Go to the Security tab > click the alert > click "Dismiss alert" > select "Fix started" or dismiss and let Dependabot re-scan. Sometimes the alert just needs a refresh.

4. Check the alert details - Click into each alert and look at the "Patched version" field. If your merged PR updated to a version that's still below the patched version, the alert won't clear.

5. Multiple manifest files - If you have multiple package.json files (e.g., root + subdirectories), Dependabot might have fixed one but the alert persists because another manifest still has the vulnerable version.

For the picomatch alert specifically - since you just merged it today, give it a few hours. Dependabot's re-scan isn't instant after merge.

[pachewise]

Issue was I had a package-lock.json file that I wasn't using (and therefore wasn't being updated by dependabot). So #1 in your list.