Skip to content

fix: split Renovate node artifact updates #1052

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
Merged

fix: split Renovate node artifact updates #1052

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
20 changes: 11 additions & 9 deletions .github/renovate.json5
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -135,18 +135,20 @@
{
// 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.
// before regenerating bun.lock. That fails in this environment; the
// postUpgradeTasks `bun install` below regenerates bun.lock instead.
matchManagers: ['bun', 'npm'],
skipArtifactsUpdate: true,
},
{
// @types/node must not be grouped with Docker/custom-manager Node surfaces:
// skipArtifactsUpdate only suppresses artifact regeneration when every
// upgrade in the group carries the flag, so mixed-manager Node groups still
// hit the failing bun installer path.
matchManagers: ['npm'],
matchPackageNames: ['@types/node'],
groupName: null,
},
{matchFileNames: ['.github/workflows/**'], semanticCommitType: 'ci'},
{matchDatasources: ['docker'], semanticCommitType: 'build'},
{
Expand Down
Loading