Dependabot runs security updates for pip when updates are configured for uv

[sgerrand]

Select Topic Area

Bug

Body

I have a repository which is configured to use uv as the package ecosystem for Python dependencies. It was previously configured to use pip but that was changed ~ 3 months ago. Dependabot creates updates for Python packages using uv without any problems but it continues to use pip for security updates.

How can I update Dependabot's configuration for security to use uv instead of pip as the package ecosystem?

The content of the relevant dependabot.yml file follows:

# Please see the documentation for all configuration options:# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-fileversion: 2updates: - package-ecosystem: "github-actions"directory: "/"schedule: interval: "weekly"cooldown: default-days: 7 - package-ecosystem: "npm"directory: "/"schedule: interval: "weekly"cooldown: default-days: 7semver-patch-days: 3groups: security-dependencies-development: applies-to: "security-updates"dependency-type: "development"security-dependencies-production: applies-to: "security-updates"dependency-type: "production"production-dependencies: applies-to: "version-updates"dependency-type: "production"development-dependencies: applies-to: "version-updates"dependency-type: "development"ignore: - dependency-name: "tailwindcss"# Tailwind CSS v4 is incompatible with eslint-plugin-tailwindcssversions: ["4.x"] - package-ecosystem: "uv"directory: "/"schedule: interval: "weekly"cooldown: default-days: 7semver-patch-days: 3groups: security-dependencies: applies-to: "security-updates"patterns: - "*"production-dependencies: exclude-patterns: - "ipykernel" - "pandas-ods-reader" - "playwright*" - "pyflakes" - "pytest*" - "ruff" - "tox*"development-dependencies: patterns: - "ipykernel" - "pandas-ods-reader" - "playwright*" - "pyflakes" - "pytest*" - "ruff" - "tox*"

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

[sgerrand]

I filed a bug for this behaviour in dependabot/dependabot-core but haven't had any response from the team there. 😞

[maurofaccenda]

I have the same problem. At first I thought it was because the dependabot.yml was commited later and Dependabot assumed pip by default. But even after recreating the repository from scratch, making sure the dependabot.yml with only uv ecosystem is included from the first commit, the same happened. And even after some PRs using uv had been created, there were some other with pip.

[sgerrand]

Sorry to hear that you've experienced the same problem but (selfishly) I'm glad that I'm not the only one.

[maurofaccenda]

Sorry to hear that you've experienced the same problem but (selfishly) I'm glad that I'm not the only one.

No worries man. That's always reassuring. Now you know it is not personall 😄