Skip to content

docs(ci): record why the bun dependabot run currently fails - #331

Open
keonik wants to merge 1 commit into
mainfrom
chore/dependabot-bun-note
Open

docs(ci): record why the bun dependabot run currently fails#331
keonik wants to merge 1 commit into
mainfrom
chore/dependabot-bun-note

Conversation

@keonik

@keonik keonik commented Sep 4, 2026

Copy link
Copy Markdown
Owner

Comment-only. Keeps package-ecosystem: bun and writes down why the monthly run is red so it doesn't get "fixed" by reverting #329.

The state

Dependabot::DependencyFileNotSupported
Unsupported bun.lock 'lockfileVersion' 2 in /bun.lock.
The bun version Dependabot runs supports up to 1.

bun 1.4 writes "lockfileVersion": 2; Dependabot's updater image bundles an older bun. There is no flag to make bun emit a v1 lockfile, so nothing can be done locally.

Why this error is progress

It is the fix for dependabot-core#15848, where the old image silently discarded a v2 lockfile, regenerated a v1, and changed resolutions with no warning. #15896 made it reject loudly instead. Actual v2 support is #16071 — still open, last updated 2026-08-28.

The trade being accepted

No dependency PRs until #16071 ships. Reverting to package-ecosystem: npm would restore them, but every one would arrive with a stale bun.lock and fail bun install --frozen-lockfile — exactly the noise #329 cleared. A loud monthly failure beats a stream of red PRs.

github-actions updates are unaffected and still working.

Keeping `package-ecosystem: bun`. The monthly run errors because bun 1.4
writes lockfileVersion 2 and Dependabot's bundled bun parses only
version 1 (dependabot-core#16071, open). That hard error is itself the
fix for #15848, where the old image silently downgraded the lockfile and
changed resolutions with no warning.

No dependency PRs until #16071 ships. Reverting to `npm` would bring the
PRs back but each would carry a stale lockfile and fail CI, which is the
noise #329 removed.
@keonik keonik added the skip-changeset PR intentionally needs no changeset (docs/CI only) label Sep 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changeset PR intentionally needs no changeset (docs/CI only)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant