Dependabot ignore rule are broken #210864
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 happens because of how Dependabot parses versions: it expects strict SemVer ( When a package jumps from SemVer (like To work around it, define the ignore rule directly in your version: 2
updates:
- package-ecosystem: "npm"
directory: "/"
schedule:
interval: "weekly"
ignore:
- dependency-name: "xxx"
versions: [">= 20220000"]This ignores the new CalVer range directly without relying on the SemVer chat parser. |
|
Reopen your PR to undo its comment-based ignore rule. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Dependabot
Discussion Details
"Dependabot commands and options" disappeared from new Dependabot PRs.
More importantly, "@dependabot ignore this major version" now (for a several days, maybe a bit more) ignores the base version, not proposed version:
I used to ignore the proposed version, not the current one. Previously, I used this command, as "Most Recent Ignore Conditions Applied to This Pull Request" shows:
All reactions