Skip to content

chore(dependabot): configure version updates for bun and github-actions - #122

Merged
hyperpolymath merged 2 commits into
mainfrom
chore/dependabot-config
Oct 15, 2026
Merged

hyperpolymath merged 2 commits into
mainfrom
chore/dependabot-config

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

What this changes

Adds .github/dependabot.yml — the repository never had one, which is why Dependabot produced no version updates. (The "Dependabot Updates" workflow runs that did exist were security updates, which need no config; they failed 2026-09-26..27 because the npm_and_yarn updater refuses a Bun-managed project — bun.lock with no npm/yarn/pnpm lockfile — while trying to fix alerts against the since-removed test/doi fixtures. Both alerts are already fixed.)

Configuration

Ecosystem Directory Cadence Notes
bun /frontend weekly The ecosystem Dependabot requires for bun.lock; npm_and_yarn cannot update it
github-actions / weekly Advances the full-SHA action pins; the account's allowlist policy (only actions/* and hyperpolymath/*, asserted by test/unit/test_install_pins.jl) survives, since Dependabot updates the existing pinned refs

Both grouped and prefixed chore(deps).

What Dependabot cannot cover here

Julia (Project.toml/Manifest.toml) and R (renv.lock) are not Dependabot ecosystems. Their pins are managed by config/defaults/tool_versions.yml and asserted by test/unit/test_install_pins.jl and the CI workflow — that stays the mechanism.

Testing

Config-only change; no code path is touched. Dependabot validates the file on merge and the first "Dependabot Updates" run will appear on the default branch within the hour.

Notes

The commit is unsigned — the signing key's passphrase was not available in the session that produced it.

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe vibe@mistral.ai

There was no dependabot.yml, so Dependabot never created version updates;
only security updates ran, and those (2026-09-26..27) failed because the
npm_and_yarn updater refuses a Bun-managed project while trying to fix
alerts against the since-removed test/doi fixtures. Both alerts are now
fixed and the fixtures gone.

Version updates, weekly, grouped, conventional-commit prefixed:
- "bun" for /frontend, the ecosystem Dependabot requires for bun.lock
  (the npm_and_yarn updater cannot update it).
- "github-actions" for the workflow pins, which advances the full-SHA
  pins while keeping the account's allowlist policy intact.

Julia (Project.toml/Manifest.toml) and R (renv.lock) are not Dependabot
ecosystems; their pins stay in config/defaults/tool_versions.yml, asserted
by test/unit/test_install_pins.jl.

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
@coderabbitai

coderabbitai Bot commented Oct 15, 2026

Copy link
Copy Markdown

Review in Change Stack →

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 2b1a1f26-894a-4894-9b58-7f0d9d069e26
📥 Commits

Reviewing files that changed from the base of the PR and between b672663 and 9e99807.

📒 Files selected for processing: 1
  • .github/dependabot.yml
+--------------------------------------+
| Warning: May contain traces of bugs. |
+--------------------------------------+
  \
   \   (\__/)
       (•ㅅ•)
       /   づ
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@hyperpolymath
hyperpolymath merged commit 9360cb9 into main Oct 15, 2026
6 of 7 checks passed
@hyperpolymath
hyperpolymath deleted the chore/dependabot-config branch October 15, 2026 01:06
@sonarqubecloud

Copy link
Copy Markdown

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