chore(deps): 7-day Dependabot cooldown, and re-anchor the fl_lib gitlink - #1440
Merged
Conversation
`minimumReleaseAge = 604800` in the maintainer's bunfig refuses to install anything published in the last seven days; Dependabot knew nothing about that and proposed versions the machine would then decline — #1414, #1427, #1436 and now #1438 are all the same starlight/astro upgrade arriving five days early and waiting. `cooldown: default-days: 7` on all four entries says the same thing on GitHub's side. Explicit rather than left out: unset, `default-days` is 3. GitHub applies cooldown to version updates only, never to security updates, which is the right way round — a fix for a known advisory should not sit for a week, and those PRs keep arriving the day they exist.
Contributor
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughDependabot now applies a seven-day cooldown to Cargo, Pub, npm, and GitHub Actions version updates. Security updates remain immediate. The Suggested reviewers: ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
lollipopkit/fl_lib#51 was squashed onto main as ee1c720, so the commit the gitlink named — 0024513, the PR branch's head — now lives only on a branch that is about to be deleted. The tree is byte-identical between the two; this only re-anchors the pointer onto something main can reach.
lollipopkit
marked this pull request as ready for review
September 7, 2026 13:42
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
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.
Two unrelated one-liners, kept together rather than as two PRs.
Cooldown
minimumReleaseAge = 604800in the maintainer's bunfig refuses to install anything published in the last seven days. Dependabot knew nothing about that and kept proposing versions the machine would then decline — #1414, #1427, #1436 and now #1438 are all the same starlight/astro upgrade, arriving five days early and sitting there.on all four entries. Explicit rather than omitted: with
cooldownunset the default is 3 days, andsemver-major-days/-minor-/-patch-fall back todefault-dayswhen not given, so one line covers every bump type.Security updates are unaffected, by GitHub's design rather than by anything here: cooldown applies to version updates only. That is the right way round — a fix for a known advisory should not wait a week, and #1424, #1432 and #1439 were all merged the day they existed.
Validated against SchemaStore's
dependabot-2.0.json: 0 errors. Every ecosystem used here (cargo, pub, npm, github-actions) is in GitHub's cooldown support table.fl_lib gitlink
lollipopkit/fl_lib#51 was squashed onto that repository's main as
ee1c720. The gitlink still named0024513— the PR branch's head, which once that branch is deleted is reachable from nothing on main. Every checkout here usessubmodules: recursive, so that is the whole CI rather than one job.The two commits have an identical tree (
git diff ee1c7200 0024513is empty), so no code changes; it only re-anchors the pointer. Merging this is what makes deletingfeat/update-machine-archin fl_lib safe.Summary by CodeRabbit