Skip to content

fix: skip Renovate bun lock artifacts for npm updates #1050

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
marcusrbrown merged 1 commit into from
Jun 27, 2026
+12 −10
Merged

fix: skip Renovate bun lock artifacts for npm updates #1050

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 12 additions & 10 deletions .github/renovate.json5
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,16 +133,18 @@
],
packageRules: [
{
// The Renovate runner image (bfra-me/renovate-action) curl-installs Bun
// globally as root and runs Renovate as a non-root user, so the bun
// manager's lockfile regeneration (`install-tool bun <ver>` →
// updateArtifacts) fails EACCES writing the root-owned containerbase tool
// dir — failing the `renovate/artifacts` check on every branch, for any
// version. Skip Renovate's bun artifact update; the `postUpgradeTasks`
// `bun install` below regenerates bun.lock on the runner's installed Bun,
// so the lockfile still stays current. Dependency update PRs are
// unaffected. Remove if the runner switches to binarySource=global.
matchManagers: ['bun'],
// bfra-me/renovate-action sets RENOVATE_BINARY_SOURCE=install, so
// Renovate's built-in artifact update path calls `install-tool bun <ver>`
// (containerbase) to obtain Bun before regenerating bun.lock. That call
// fails in the self-hosted action environment, causing the
// `renovate/artifacts` synthetic status to fail on every branch.
// This affects both the `bun` manager (direct lockfile updates) and the
// `npm` manager (package.json dep updates that also touch bun.lock).
// Skip Renovate's built-in artifact update for both; the `postUpgradeTasks`
// `bun install` below regenerates bun.lock using the runner's pre-installed
// Bun, so the lockfile still stays current. Remove if the runner switches
// to binarySource=global or containerbase gains a working bun installer.
matchManagers: ['bun', 'npm'],
skipArtifactsUpdate: true,
},
{matchFileNames: ['.github/workflows/**'], semanticCommitType: 'ci'},
Expand Down
Loading