chore(deps): update all devdependencies#272
Conversation
⚠ Artifact update problemRenovate 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:
The artifact failure details are included below: File name: yarn.lock |
svc-secops
force-pushed
the
renovate/all-dev
branch
from
bc730f8 to
4757460
Compare
svc-secops
changed the title
svc-secops
force-pushed
the
renovate/all-dev
branch
from
4757460 to
ac46a73
Compare
❌ Deploy Preview for apollo-client-nextjs-docmodel failed.
|
svc-secops
force-pushed
the
renovate/all-dev
branch
from
ac46a73 to
4314925
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
4314925 to
2ee1e0a
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
2ee1e0a to
ad44c80
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
ad44c80 to
eb7f86a
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
eb7f86a to
ac0dcf3
Compare
|
svc-secops
force-pushed
the
renovate/all-dev
branch
from
ac0dcf3 to
b2a5e60
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
b2a5e60 to
263a2da
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
263a2da to
1aed9f6
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
1aed9f6 to
fe2fefb
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
fe2fefb to
fd30c7b
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
8377935 to
494a58a
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
494a58a to
fadbc07
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
fadbc07 to
696b3dd
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
696b3dd to
89136f8
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
89136f8 to
04e4cdf
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
04e4cdf to
5c43307
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
5c43307 to
a741fff
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
a741fff to
c72d32f
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
c72d32f to
27376ca
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
27376ca to
eb93096
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
eb93096 to
99c3c4b
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
99c3c4b to
28ca86d
Compare
svc-secops
force-pushed
the
renovate/all-dev
branch
from
28ca86d to
f00d440
Compare
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughMultiple package.json files updated to bump devDependency versions and tighten caret ranges to exact pins (notably Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@package.json`:
- Around line 45-46: Update package.json so the dependency "@yarnpkg/core"
matches the CLI version "@yarnpkg/cli" by changing "@yarnpkg/core" to "4.9.1"
and then regenerate the lockfile (run the repository's standard yarn
install/lockfile generation command) so the lockfile reflects the aligned Yarn
v4 versions; ensure the change targets the package.json entry for
"@yarnpkg/core" and that the updated yarn.lock (or generated lockfile) is
committed.
In `@packages/package.json`:
- Around line 9-11: Update the package dependency for eslint-plugin-react-hooks
in package.json from 4.6.2 to a 6.1.0+ release to resolve the ESLint 9
peer-dependency conflict and enable React Compiler diagnostics; modify the
dependency string for "eslint-plugin-react-hooks" to "6.1.0" (or a later 6.x
stable) and run your package manager install and lint to verify compatibility
with ESLint 9 and existing ESLint config.
ℹ️ Review info
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (7)
package.jsonpackages/client-react-streaming/package.jsonpackages/experimental-nextjs-app-support/package.jsonpackages/nextjs/package.jsonpackages/package.jsonpackages/react-router/package.jsonpackages/tanstack-start/package.json
| "@yarnpkg/cli": "4.9.1", | ||
| "@yarnpkg/core": "4.2.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify Yarn package alignment and lockfile presence/status
jq -r '.packageManager, .devDependencies["@yarnpkg/cli"], .devDependencies["@yarnpkg/core"]' package.json
fd '^yarn.lock$'
git status --short -- yarn.lock package.jsonRepository: apollographql/apollo-client-integrations
Length of output: 116
🌐 Web query:
@yarnpkg/cli 4.9.1 @yarnpkg/core 4.2.0 compatibility
💡 Result:
@yarnpkg/cli and @yarnpkg/core aren’t intended to be mixed-and-matched across different Yarn releases. The CLI is explicitly “built on top of” the core package and is responsible for hydrating a project and injecting the built-in plugins, so it relies on @yarnpkg/core internals being in sync with it. [1][2]
So @yarnpkg/cli@4.9.1 + @yarnpkg/core@4.2.0 is not a supported/guaranteed-compatible combination (even though both are Yarn v4). [1][2]
What to do instead
- Use a matched set (recommended): upgrade
@yarnpkg/coreto the same release line as the CLI (i.e., align with the Yarn 4.9.x toolchain), or - Downgrade
@yarnpkg/clito 4.2.0 to match your current@yarnpkg/core@4.2.0. [3]
Sources:
[1] https://yarnpkg.com/advanced/architecture
[2] https://classic.yarnpkg.com/en/package/%40yarnpkg/sdks
[3] https://www.npmjs.com/package/%40yarnpkg/cli/v/4.9.1?activeTab=versions
🌐 Web query:
Yarn package version alignment requirements cli core
💡 Result:
@yarnpkg/cliis the CLI entry point built on top of@yarnpkg/core, so they’re intended to be used as a coordinated set rather than mixed arbitrarily across majors/minors. [1]- In practice, the hard “alignment requirement” is: stay on the same major line and satisfy peer-dependency ranges (this is how Yarn’s own plugins declare compatibility with
@yarnpkg/cliand@yarnpkg/core). For example,@yarnpkg/plugin-interactive-toolsdeclares peer deps like@yarnpkg/cli: ^4.5.1and@yarnpkg/core: ^4.1.4(compatible v4 range, not necessarily identical versions). [3] - Yarn’s own published package set also reflects that versions may differ within the same major (e.g., the API page lists
@yarnpkg/cli v4.12.0and@yarnpkg/core v4.5.0). [2]
Rule of thumb: don’t mix @yarnpkg/* across majors (e.g., @yarnpkg/cli@4 with @yarnpkg/core@3), and when you add plugins/aux packages, make sure all @yarnpkg/* satisfy the plugins’ peerDependencies ranges. [3]
Sources: [1] [2] [3]
Align @yarnpkg/core to 4.9.1 before merge and regenerate lockfile.
The current versions—@yarnpkg/cli@4.9.1 paired with @yarnpkg/core@4.2.0—form an unsupported combination. The CLI is built on top of core and relies on core internals being in sync; these mismatched versions across Yarn's v4 release cycle can cause artifact generation failures and lockfile instability.
Suggested fix
- "@yarnpkg/core": "4.2.0",
+ "@yarnpkg/core": "4.9.1",📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "@yarnpkg/cli": "4.9.1", | |
| "@yarnpkg/core": "4.2.0", | |
| "@yarnpkg/cli": "4.9.1", | |
| "@yarnpkg/core": "4.9.1", |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@package.json` around lines 45 - 46, Update package.json so the dependency
"@yarnpkg/core" matches the CLI version "@yarnpkg/cli" by changing
"@yarnpkg/core" to "4.9.1" and then regenerate the lockfile (run the
repository's standard yarn install/lockfile generation command) so the lockfile
reflects the aligned Yarn v4 versions; ensure the change targets the
package.json entry for "@yarnpkg/core" and that the updated yarn.lock (or
generated lockfile) is committed.
| "eslint": "8.57.1", | ||
| "eslint-plugin-react": "7.37.5", | ||
| "eslint-plugin-react-hooks": "4.6.2" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check current eslint-plugin-react-hooks version and React 19.2 APIs usage
jq -r '.devDependencies["eslint-plugin-react-hooks"]' packages/package.json
echo "---"
# Also check React version
jq -r '.dependencies["react"]' packages/package.json
echo "---"
# Search for React 19.2 hook semantics
rg -nP -t ts -t tsx '\buseEffectEvent\b|<Activity\b|\bcacheSignal\b' --max-count=10Repository: apollographql/apollo-client-integrations
Length of output: 147
🌐 Web query:
eslint-plugin-react-hooks v6 React 19 compatibility release
💡 Result:
eslint-plugin-react-hooks v6 “React 19/Compiler-compatible” release is eslint-plugin-react-hooks@6.1.0 (the first official 6.x major release). The React team notes that 6.0.0 was mistakenly published and immediately deprecated/untagged, and 6.1.0 is the intended stable 6.x line with breaking changes (notably Node.js ≥ 18 and flat config as the default recommended preset, with legacy moved to recommended-legacy) plus new/updated rules covering newer React APIs/patterns (e.g., use, useEffectEvent, etc.). [1]
React’s docs also describe that eslint-plugin-react-hooks now surfaces React Compiler diagnostics (in addition to classic hooks rules), which is part of what people mean by “React 19 compatibility.” [2]
If you’re upgrading: avoid 6.0.0 and target ^6.1.0 (or newer 6.x) instead. [1][3]
Sources
[1] https://github.com/facebook/react/releases (entry: eslint-plugin-react-hooks@6.1.0)
[2] https://react.dev/reference/eslint-plugin-react-hooks
[3] react/react#34647
🏁 Script executed:
#!/bin/bash
# Check for React 19 specific APIs more broadly
rg -n 'useEffectEvent|cacheSignal|Activity|use(' --type-list | head -5
echo "---"
# Check actual React version in monorepo (likely at root or in workspace packages)
fd package.json -x grep -l '"react"' {}
echo "---"
# List root and immediate package.json files to understand structure
ls -la | grep -E '^-.*package\.json'
cat package.json 2>/dev/null | jq -r '.dependencies["react"], .devDependencies["react"]' | head -2Repository: apollographql/apollo-client-integrations
Length of output: 1254
🌐 Web query:
eslint-plugin-react-hooks 4.6.2 React 19 support limitations
💡 Result:
eslint-plugin-react-hooks@4.6.2 works fine for “classic” Hooks linting, but it has these practical React 19-era limitations:
- No ESLint 9 support (install/peer-dep conflict): 4.6.2 declares a peer dependency range that excludes ESLint 9, so upgrading your toolchain to ESLint 9 (common in newer setups) will fail or require
--legacy-peer-deps/ overrides. [1] - No React 19
useEffectEvent-aware linting: React 19’suseEffectEventcomes with specific lint-enforced rules (e.g., don’t put Effect Events in dependency arrays; don’t call them outside Effects / Effect Events). Those lint behaviors are described in the React docs and are enforced by newer plugin versions; 4.6.2 won’t understand/enforce these semantics correctly (leading to missing errors or wrong warnings). [2] - No React Compiler diagnostics / newer rule set: Newer
eslint-plugin-react-hooksversions include additional rules and React Compiler diagnostics surfaced through the plugin; 4.6.2 predates that expanded scope (it’s basically justrules-of-hooks+exhaustive-deps). [3] - In practice, React 19 guidance expects upgrading the plugin: Community/React-ecosystem guidance around React 19.x notes updated
eslint-plugin-react-hooksreleases to align linting with new features likeuseEffectEvent. [4]
Sources: [1] [2] [3] [4] (github.com)
Citations:
🏁 Script executed:
cat package.json | jq '.dependencies["react"], .devDependencies["react"]'Repository: apollographql/apollo-client-integrations
Length of output: 93
Upgrade eslint-plugin-react-hooks to v6.1.0+ for ESLint 9 and React Compiler support.
Line 11 keeps eslint-plugin-react-hooks at 4.6.2, which has a peer-dependency conflict with ESLint 9 and lacks React Compiler diagnostics. Upgrade to v6.1.0 (the stable 6.x release; v6.0.0 was deprecated) to maintain compatibility with modern tooling and gain React Compiler integration.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/package.json` around lines 9 - 11, Update the package dependency for
eslint-plugin-react-hooks in package.json from 4.6.2 to a 6.1.0+ release to
resolve the ESLint 9 peer-dependency conflict and enable React Compiler
diagnostics; modify the dependency string for "eslint-plugin-react-hooks" to
"6.1.0" (or a later 6.x stable) and run your package manager install and lint to
verify compatibility with ESLint 9 and existing ESLint config.
1 participant
This PR contains the following updates:
0.15.3->0.18.27.24.3->7.30.17.30.4(+2)7.43.2->7.58.37.58.6(+2)11.1.2->11.2.011.1.2->11.2.011.1.2->11.2.0^1.132.47->1.132.47^1.132.48->1.132.48^1.132.47->1.132.47^10.4.0->10.4.0^16.1.0->16.2.01.0.6->1.0.13^4.9.1->4.9.1^4.2.0->4.2.08.57.0->8.57.17.34.1->7.37.54.6.0->4.6.2^16.10.0->16.13.2*->16.13.224.0.0->24.1.3^5.43.1->5.43.1^21.0.3->21.0.30.2.7->0.3.18^5.0.0->5.0.04.0.13->4.1.25.0.5->5.0.10^7.8.2->7.8.211.1.2->11.2.04.7.1->4.21.05.4.5->5.9.3^5.7.3->5.7.3Release Notes
arethetypeswrong/arethetypeswrong.github.io (@arethetypeswrong/cli)
v0.18.2Patch Changes
58dca0c]v0.18.1Compare Source
Patch Changes
a4dc8a6]v0.18.0Compare Source
Minor Changes
5dd9c0b: Requiring Node.js 20 for using latest lru-cache.Patch Changes
5dd9c0b]v0.17.4Compare Source
Patch Changes
f118862]v0.17.3Compare Source
Patch Changes
e3c775e]v0.17.2Compare Source
Patch Changes
59940cd]v0.17.1Compare Source
Patch Changes
1bfc877: Fix typo in MissingExportEquals messagedb6464d: Fix minor typos55544ac: Fix truncated stdout when piping more than 64kb to another process5f96cdc]def786e]1bfc877]db6464d]v0.17.0Compare Source
Patch Changes
e7ac94c]v0.16.4Compare Source
Patch Changes
3ca2866]v0.16.3Compare Source
Patch Changes
66ada51: Fix warning message json-format suggestion to use proper syntaxv0.16.2Compare Source
Patch Changes
622b71f]v0.16.1Compare Source
Patch Changes
5ee6f29: Update README with new problem kindv0.16.0Compare Source
Minor Changes
d480f1c: New problem kind: Named exports cannot be detected by Node.js. Thanks @laverdet!Patch Changes
970b141]d480f1c]v0.15.4Compare Source
Patch Changes
5566c1b: Upgrading marked-terminal to version 7.1.0microsoft/rushstack (@microsoft/api-documenter)
v7.30.1Compare Source
Fri, 17 Apr 2026 15:14:57 GMT
Version update only
v7.30.0Compare Source
Fri, 10 Apr 2026 22:46:34 GMT
Minor changes
v7.29.11Compare Source
Thu, 09 Apr 2026 00:15:07 GMT
Version update only
v7.29.10Compare Source
Sat, 04 Apr 2026 00:14:00 GMT
Version update only
v7.29.9Compare Source
Wed, 01 Apr 2026 15:13:38 GMT
Version update only
v7.29.8Compare Source
Tue, 31 Mar 2026 15:14:14 GMT
Version update only
v7.29.7Compare Source
Mon, 09 Mar 2026 15:14:08 GMT
Version update only
v7.29.6Compare Source
Wed, 25 Feb 2026 21:39:42 GMT
Version update only
v7.29.5Compare Source
Wed, 25 Feb 2026 00:34:29 GMT
Version update only
v7.29.4Compare Source
Tue, 24 Feb 2026 01:13:27 GMT
Version update only
v7.29.3Compare Source
Mon, 23 Feb 2026 00:42:21 GMT
Version update only
v7.29.2Compare Source
Fri, 20 Feb 2026 16:14:49 GMT
Version update only
v7.29.1Compare Source
Thu, 09 Apr 2026 00:15:07 GMT
Version update only
v7.29.0Compare Source
Thu, 19 Feb 2026 00:04:52 GMT
Minor changes
lib-commonjs, DTS is now underlib-dts, and ESM is now underlib-esm. Imports tolibstill work as before, handled by the"exports"field inpackage.json.v7.28.9Compare Source
Sat, 07 Feb 2026 01:13:26 GMT
Version update only
v7.28.8Compare Source
Wed, 04 Feb 2026 20:42:47 GMT
Version update only
v7.28.7Compare Source
Wed, 04 Feb 2026 16:13:27 GMT
Version update only
v7.28.6Compare Source
Fri, 30 Jan 2026 01:16:13 GMT
Version update only
v7.28.5Compare Source
Thu, 08 Jan 2026 01:12:30 GMT
Version update only
v7.28.2Compare Source
Sat, 06 Dec 2025 01:12:28 GMT
Version update only
v7.28.1Compare Source
Fri, 21 Nov 2025 16:13:56 GMT
Version update only
v7.28.0Compare Source
Wed, 12 Nov 2025 01:12:56 GMT
Minor changes
@microsoft/tsdocdependency to~0.16.0.v7.27.4Compare Source
Tue, 04 Nov 2025 08:15:14 GMT
Version update only
v7.27.3Compare Source
Fri, 24 Oct 2025 00:13:38 GMT
Version update only
v7.27.2Compare Source
Wed, 22 Oct 2025 00:57:54 GMT
Version update only
v7.27.1Compare Source
Wed, 08 Oct 2025 00:13:28 GMT
Version update only
v7.27.0Compare Source
Fri, 03 Oct 2025 20:09:59 GMT
Minor changes
node:protocol.v7.26.36Compare Source
Tue, 30 Sep 2025 23:57:45 GMT
Version update only
v7.26.35Compare Source
Tue, 30 Sep 2025 20:33:50 GMT
Patches
js-yamldependencyv7.26.34Compare Source
Fri, 12 Sep 2025 15:13:07 GMT
Version update only
v7.26.33Compare Source
Thu, 11 Sep 2025 00:22:31 GMT
Version update only
v7.26.32Compare Source
Tue, 19 Aug 2025 20:45:02 GMT
Version update only
v7.26.31Compare Source
Fri, 01 Aug 2025 00:12:48 GMT
Version update only
v7.26.30Compare Source
Wed, 23 Jul 2025 20:55:57 GMT
Version update only
v7.26.29Compare Source
Tue, 24 Jun 2025 00:11:43 GMT
Patches
v7.26.28Compare Source
Sat, 21 Jun 2025 00:13:15 GMT
Version update only
v7.26.27Compare Source
Tue, 13 May 2025 02:09:20 GMT
Version update only
v7.26.26Compare Source
Thu, 01 May 2025 15:11:33 GMT
Version update only
v7.26.25Compare Source
Thu, 01 May 2025 00:11:12 GMT
Version update only
v7.26.24Compare Source
Fri, 25 Apr 2025 00:11:32 GMT
Version update only
v7.26.23Compare Source
Mon, 21 Apr 2025 22:24:25 GMT
Version update only
v7.26.22Compare Source
Thu, 17 Apr 2025 00:11:21 GMT
Version update only
v7.26.21Compare Source
Tue, 15 Apr 2025 15:11:57 GMT
Version update only
v7.26.20Compare Source
Wed, 09 Apr 2025 00:11:02 GMT
Version update only
v7.26.19Compare Source
Fri, 04 Apr 2025 18:34:35 GMT
Version update only
v7.26.18Compare Source
Tue, 25 Mar 2025 15:11:15 GMT
Version update only
v7.26.17Compare Source
Wed, 12 Mar 2025 22:41:36 GMT
Version update only
v7.26.16Compare Source
Wed, 12 Mar 2025 00:11:31 GMT
Version update only
v7.26.15Compare Source
Tue, 11 Mar 2025 02:12:33 GMT
Version update only
v7.26.14Compare Source
Tue, 11 Mar 2025 00:11:25 GMT
Version update only
v7.26.13Compare Source
Sat, 01 Mar 2025 05:00:09 GMT
Version update only
v7.26.12Compare Source
Thu, 27 Feb 2025 01:10:39 GMT
Version update only
v7.26.11Compare Source
Wed, 26 Feb 2025 16:11:11 GMT
Version update only
v7.26.10Compare Source
Sat, 22 Feb 2025 01:11:11 GMT
Version update only
v7.26.9Compare Source
Wed, 19 Feb 2025 18:53:48 GMT
Version update only
v7.26.8Compare Source
Wed, 12 Feb 2025 01:10:52 GMT
Version update only
v7.26.7Compare Source
Thu, 30 Jan 2025 16:10:36 GMT
Version update only
v7.26.6Compare Source
Thu, 30 Jan 2025 01:11:42 GMT
Version update only
v7.26.5Compare Source
Thu, 09 Jan 2025 01:10:10 GMT
Version update only
v7.26.4Compare Source
Tue, 07 Jan 2025 22:17:32 GMT
Version update only
v7.26.3Compare Source
Tue, 30 Sep 2025 23:57:45 GMT
Version update only
v7.26.2Compare Source
Tue, 24 Jun 2025 00:11:43 GMT
Patches
v7.26.1Compare Source
Fri, 04 Apr 2025 18:34:35 GMT
Version update only
v7.26.0Compare Source
Sat, 23 Nov 2024 01:18:55 GMT
Minor changes
v7.25.22Compare Source
Fri, 22 Nov 2024 01:10:43 GMT
Version update only
v7.25.21Compare Source
Thu, 24 Oct 2024 00:15:47 GMT
Version update only
v7.25.20Compare Source
Mon, 21 Oct 2024 18:50:09 GMT
Version update only
v7.25.19Compare Source
Thu, 17 Oct 2024 08:35:06 GMT
Version update only
v7.25.18Compare Source
Tue, 15 Oct 2024 00:12:31 GMT
Version update only
v7.25.17Compare Source
Wed, 02 Oct 2024 00:11:19 GMT
Version update only
v7.25.16Compare Source
Tue, 01 Oct 2024 00:11:28 GMT
Version update only
v7.25.15Compare Source
Mon, 30 Sep 2024 15:12:19 GMT
Version update only
v7.25.14Compare Source
Fri, 13 Sep 2024 00:11:42 GMT
Version update only
v7.25.13Compare Source
Tue, 10 Sep 2024 20:08:11 GMT
Version update only
v7.25.12[Compare Source](https://redirect.github.com/microsoft/rushstack/compare/@microsoft/api-documenter_v7.25.11...@m
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 8am and before 4pm on tuesday" in timezone Etc/UTC.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.