Update dependency @probot/octokit-plugin-config to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@probot/octokit-plugin-config	^3.0.2 → ^4.0.0

---

Release Notes

probot/octokit-plugin-config (@​probot/octokit-plugin-config)

v4.1.0

Compare Source

Features

• replace js-yaml with yaml (#​297) (14e9b82)

v4.0.0

Compare Source

Bug Fixes

• deps: update octokit monorepo (major) (#​270) (ba7086e)

BREAKING CHANGES

• deps: Drop support for Node 18 and 21

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: transfer-issue-webhook@1.0.0
npm ERR! Found: @octokit/core@6.1.6
npm ERR! node_modules/@octokit/core
npm ERR!   @octokit/core@"^6.1.4" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @octokit/core@">=7" from @probot/octokit-plugin-config@4.1.0
npm ERR! node_modules/@probot/octokit-plugin-config
npm ERR!   @probot/octokit-plugin-config@"^4.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-01-08T17_59_36_083Z-debug-0.log