From 1a0a327b81bea0bc9d2d4e370f5efa686739d4cd Mon Sep 17 00:00:00 2001 From: tannevaled Date: Mon, 16 Nov 2026 18:26:13 +0000 Subject: [PATCH 1/2] chore(deps): update renovatebot/github-action action to v46.3.14 --- .github/workflows/renovate.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/renovate.yml b/.github/workflows/renovate.yml index d48f3f1..a58144f 100644 --- a/.github/workflows/renovate.yml +++ b/.github/workflows/renovate.yml @@ -22,7 +22,7 @@ jobs: steps: - uses: actions/checkout@v7 - name: Run Renovate - uses: renovatebot/github-action@v46.3.13 + uses: renovatebot/github-action@v46.3.14 with: configurationFile: config.js token: ${{ secrets.RENOVATE_TOKEN }} From 083d22c30228d335d8cf970e23aa49eac67a7ad3 Mon Sep 17 00:00:00 2001 From: tannevaled Date: Fri, 20 Nov 2026 08:35:39 +0100 Subject: [PATCH 2/2] config: dependencyDashboard is an object in Renovate 46.3.14 The bot's own pull request bumping renovatebot/github-action to v46.3.14 goes RED on `validate`, and stays red until this line is written the new way. From the failing job's log: - "dependencyDashboard": true, + "dependencyDashboard": { + "enabled": true + }, ##[error]Process completed with exit code 1. Renovate now reports the boolean form as a config needing migration and exits 1 on it. Read, not inferred. The control is in the same repository at the same time: the open node bump (#24) passed the SAME `validate` lane while this one failed, which is what says the cause is the config and not the runner or the lane. Co-Authored-By: Claude Opus 5 --- config.js | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/config.js b/config.js index 5eb8cbd..2ee8482 100644 --- a/config.js +++ b/config.js @@ -19,7 +19,18 @@ module.exports = { autodiscoverFilter: ['go-embedded-ruby/**'], onboarding: false, requireConfig: 'optional', - dependencyDashboard: true, + // An OBJECT, not the boolean it used to be. Renovate 46.3.14 reports the + // boolean form as a config needing migration and prints the diff + // + // - "dependencyDashboard": true, + // + "dependencyDashboard": { "enabled": true }, + // + // then exits 1 — so the bot's OWN pull request bumping the action is the one + // that goes red, and the lane stays red until this line is written the new + // way. Read from the failing job's log, not inferred: the node bump open at + // the same time passed the same lane, which is what says it is this and not + // the runner. + dependencyDashboard: { enabled: true }, repositoryCache: 'enabled', // default.json beside this file is a PRESET, and a preset reaches a // repository only through an `extends` that names it. Sitting in the