@256BitChris There's a delicate line here, especially recently. Here's our take and the new default behavior for version updates: https://t.co/NTwt2Yddcb wdyt?
Dependabot alerts now cover more ecosystems by ingesting malware advisories from the OpenSSF malicious-packages repository.
• Expanded malware data includes npm, PyPI, and more ecosystems
https://t.co/hZS2a7NEQe
4. Enable Dependabot and dependency review
Your project includes code from every package it depends on.
Dependabot alerts you to known vulnerabilities. Dependency review shows what a pull request adds or upgrades and whether those changes introduce vulnerable dependencies.
You can read more about why Dependabot now waits three days before issuing version update pull requests, and how that short wait can help keep malicious releases out of your code. In other words, why cooldowns are...cool https://t.co/NTwt2Yddcb
@headius 2. If labels are what you’re after, the Labeler action can apply them automatically, and you can customize this to label Dependabot's PRs however you choose: https://t.co/5NUcbJS02I
@headius Hi! A few ideas: 1. would fewer PRs containing the same updates help? Dependabot supports groups for version and security updates. You can also control updates by package or directory, customize schedules, and more in dependabot.yml: https://t.co/7t10Ahe2Ps
tl;dr in 60 days, alerts closed 2 or more years ago are moving to archival storage. you will still be able to download them if you need them. https://t.co/eqNoR7jnFf