Skip to content

chore(deps): 7-day Dependabot cooldown, and re-anchor the fl_lib gitlink - #1440

Merged
lollipopkit merged 2 commits into
mainfrom
chore/dependabot-cooldown
Sep 7, 2026
Merged

chore(deps): 7-day Dependabot cooldown, and re-anchor the fl_lib gitlink#1440
lollipopkit merged 2 commits into
mainfrom
chore/dependabot-cooldown

Conversation

@lollipopkit

@lollipopkit lollipopkit commented Sep 7, 2026

Copy link
Copy Markdown
Owner

Two unrelated one-liners, kept together rather than as two PRs.

Cooldown

minimumReleaseAge = 604800 in 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.

    cooldown:
      default-days: 7

on all four entries. Explicit rather than omitted: with cooldown unset the default is 3 days, and semver-major-days/-minor-/-patch- fall back to default-days when 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 named 0024513 — the PR branch's head, which once that branch is deleted is reachable from nothing on main. Every checkout here uses submodules: recursive, so that is the whole CI rather than one job.

The two commits have an identical tree (git diff ee1c7200 0024513 is empty), so no code changes; it only re-anchors the pointer. Merging this is what makes deleting feat/update-machine-arch in fl_lib safe.

Summary by CodeRabbit

  • Chores
    • Dependency updates are now subject to a seven-day cooldown to help provide more predictable update timing.
    • Security-related updates remain exempt from the cooldown for faster delivery.
    • Updated supporting components to incorporate the latest available improvements.

`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.
@coderabbitai

coderabbitai Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Essentials

Run ID: 266b9530-9f1e-44f1-bbae-159bfecd529d

📥 Commits

Reviewing files that changed from the base of the PR and between 29a4660 and b7706f8.

📒 Files selected for processing (2)
  • .github/dependabot.yml
  • packages/fl_lib

📝 Walkthrough

Walkthrough

Dependabot now applies a seven-day cooldown to Cargo, Pub, npm, and GitHub Actions version updates. Security updates remain immediate. The packages/fl_lib submodule pointer now references commit ee1c7200c95bfc9d692b5dc48960155c8115930c.

Suggested reviewers: gt-610

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/dependabot-cooldown

Comment @coderabbitai help to get the list of available commands.

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 lollipopkit changed the title chore(deps): hold Dependabot to the same 7-day cooldown as the machine chore(deps): 7-day Dependabot cooldown, and re-anchor the fl_lib gitlink Sep 7, 2026
@lollipopkit
lollipopkit marked this pull request as ready for review September 7, 2026 13:42
@lollipopkit
lollipopkit merged commit 11358ab into main Sep 7, 2026
15 checks passed
@lollipopkit
lollipopkit deleted the chore/dependabot-cooldown branch September 7, 2026 13:42
@coderabbitai
coderabbitai Bot requested a review from GT-610 September 7, 2026 13:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant