No cooldown, because the default one proposes downgrades - #165
Merged
Conversation
Dependabot offered this repository a downgrade again on 2026-09-09, minutes after the last change to `dependabot.yml` was merged, and every one of them was closed and came back. The cause is the cooldown GitHub applies when the key is absent: three days, during which every release younger than that is dropped, the pinned one included, and the highest version left is offered. For a package pinned by tag and released more than once a week, that is the version below the pin. Every offer this week was the newest release older than three days at that hour. That contradicts what the file said. The meta-model paragraph claimed the downgrade does not recur while every recent tag carries a Release; all sixty-nine design tags carry one and it recurred anyway. So `cooldown: default-days: 0` is stated on the npm entry, with the reason above it, and the two group paragraphs shrink to the rule and a pointer. Nothing is lost by zero: the pins are editorial and move when the owner decides, so the cooldown protected nothing here. Siblings: companygraph/companygraph.github.io and guestgraph/guestgraph.github.io, same branch name Verified: the YAML parses; conventions-check and conventions-sync check pass. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
Dependabot offered this repository a downgrade again on 2026-09-09, minutes after the last change to
dependabot.ymlwas merged, and every one of them was closed and came back. The cause is the cooldown GitHub applies when the key is absent: three days, during which every release younger than that is dropped, the pinned one included, and the highest version left is offered. For a package pinned by tag and released more than once a week, that is the version below the pin. Every offer this week was the newest release older than three days at that hour.That contradicts what the file said. The meta-model paragraph claimed the downgrade does not recur while every recent tag carries a Release; all sixty-nine design tags carry one and it recurred anyway. So
cooldown: default-days: 0is stated on the npm entry, with the reason above it, and the two group paragraphs shrink to the rule and a pointer. Nothing is lost by zero: the pins are editorial and move when the owner decides, so the cooldown protected nothing here.Siblings: companygraph/companygraph.github.io and guestgraph/guestgraph.github.io, same branch name
Verified: the YAML parses; conventions-check and conventions-sync check pass.
🤖 Generated with Claude Code