Skip to content

build(deps): update all non-major dependencies [automerge] - #394

Merged
renovate[bot] merged 1 commit into
mainfrom
renovate/all-non-major
Nov 20, 2026
Merged

renovate[bot] merged 1 commit into
mainfrom
renovate/all-non-major

Conversation

@renovate

@renovate renovate Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@eslint-react/eslint-plugin (source) 5.28.8 → 5.30.3 age confidence devDependencies minor 5.30.5 (+1)
@playwright/test (source) 1.64.1 → 1.65.1 age confidence devDependencies minor
@testing-library/user-event 14.6.8 → 14.6.12 age confidence devDependencies patch 14.6.13
@vitejs/plugin-react (source) 6.2.1 → 6.3.0 age confidence devDependencies minor
eslint (source) 10.14.0 → 10.15.0 age confidence devDependencies minor
eslint-plugin-react-refresh 0.5.7 → 0.5.8 age confidence devDependencies patch
jdx/mise 2026.10.19 → 2026.11.2 age confidence minor v2026.11.10 (+7)
node (source) 24.22.1 → 24.22.2 age confidence tools patch 24.22.3
pipx:checkov 3.3.30 → 3.4.3 age confidence tools minor 3.4.6 (+2)
prettier (source) 3.9.10 → 3.10.1 age confidence devDependencies minor
trivy 0.76.1 → 0.76.2 age confidence tools patch
typescript-eslint (source) 8.72.1 → 8.73.0 age confidence devDependencies minor
uv 0.13.5 → 0.13.7 age confidence tools patch 0.13.9 (+1)
vite (source) 8.3.5 → 8.3.8 age confidence devDependencies patch
wrangler (source) 4.157.0 → 4.163.0 age confidence minor 4.165.0 (+1)
zizmor 1.31.1 → 1.32.0 age confidence tools minor

Release Notes

Rel1cx/eslint-react (@​eslint-react/eslint-plugin)

v5.30.3

Compare Source

🐞 Fixes
  • react-x/set-state-in-effect: setters destructured from a TypeScript- or chain-wrapped useState call (ex: const [s, setS] = useState() as any, const [s, setS] = useState()!) are recognized again, so synchronous calls to such setters in effects are reported. (#​2117)
📝 Documentation
  • Re-verified the known-issues references for eslint-plugin-react-jsx, eslint-plugin-react-dom, and eslint-plugin-react-web-api against the current implementation, and corrected a react-x false-negative example.
  • Added netdata projects to the website's community list.
🏗️ Internal
  • Reused shared AST helpers, renamed the scope-binding helpers to isNameBoundIn*, and dropped dead code; no behavioral changes.
  • Bumped dependencies across the workspace, including eslint to 10.15.0, effect to 4.1.4, vite to 8.3.8, and nx to 24.0.6; pinned fumadocs-core/fumadocs-ui to 16.18.4 and fumadocs-mdx to 15.5.3 until an upstream regression in 16.19.0 is fixed.

Full Changelog: Rel1cx/eslint-react@v5.30.2...v5.30.3

v5.30.2

Compare Source

🐞 Fixes
  • react-web-api/no-leaked-fetch: non-global fetch calls are no longer checked: a bare fetch(...) whose name is bound by an enclosing scope (ex: a local function fetch() {}) and member calls on non-global objects (ex: api.fetch(...)) are ignored, while window.fetch(...), globalThis.fetch(...), and self.fetch(...) are still recognized. (#​2116, closes #​2072)

Full Changelog: Rel1cx/eslint-react@v5.30.1...v5.30.2

v5.30.1

Compare Source

🐞 Fixes
  • react-x/no-duplicate-key: in .map() callbacks, all statically known keys are now treated as repeating, not only bare string literals.
  • react-jsx/no-leaked-semicolon: same-line leaked semicolons after an expression container are now detected (ex: <div>{x};</div>, <div>{cond && <span />};</div>).
🏗️ Internal
  • Removed the Vercel deploy step from the release workflow.

Full Changelog: Rel1cx/eslint-react@v5.30.0...v5.30.1

v5.30.0

Compare Source

✨ New
  • @eslint-react/eslint-plugin: added the all-type-checked preset, which extends all with the rules that require type information. (#​2095)
  • @eslint-react/eslint-plugin: added the experimental @eslint-react/unstable-exhaustive-deps rule, forked from exhaustive-deps, with a hooks option modeled on Biome's useExhaustiveDependencies (closureIndex/dependenciesIndex for custom Hooks, and stableResult for stable results). The rule lives in the unified plugin's own src/rules while incubating and is enabled in the all preset (and thereby in all-type-checked). (#​1698, #​2078, #​2095) Thanks to @​dgesteves!
  • react-x/set-state-in-effect: reworked around explicit effect roots, recursive value resolution, and a synchronous call graph. Stable aliases, multi-level helpers, named setups, IIFEs, and useCallback/useMemo/useEffectEvent wrappers now share one resolution path; indirect diagnostics point at the effect-side trigger and dedupe by setter sink; async functions remain deferred. (#​2075)
  • react-x/static-components: JSX member expression tags (ex: <Namespace.Bar />) are now analyzed. (#​2114)
🐞 Fixes
  • react-x/error-boundaries: optional-chained createElement calls are recognized as JSX-like return values. (#​2084)
  • react-x/no-direct-mutation-state: state assignments in nested constructor blocks (if, loops, try, and bare blocks) are no longer reported. (#​2088)
  • react-x/no-duplicate-key: only keys that provably have a duplicate are now reported. Unique siblings in a partially duplicate group (ex: [A, B, B]) are no longer reported, and duplicates followed by a unique key (ex: [A, A, B]) are now correctly reported; keys collected through Children.toArray() and Children.map() are no longer reported; only elements returned by .map() callbacks are checked; literal keys are no longer overwritten by later keys; and .map() calls on array literals with at most one element are skipped. (#​2108)
  • react-x/no-duplicate-key: the fast-path text check now matches bare key attributes and keys separated from = by whitespace (ex: <div key />, <div key = {id} />), so such elements are no longer silently skipped.
  • react-x/no-missing-component-display-name: memo components passed to generic HOCs are recognized, so anonymous ones require a display name. (#​2084)
  • react-x/no-missing-context-display-name: the autofix now applies to exported contexts and no longer produces invalid syntax for multi-declarator declarations. (#​2088, #​2089)
  • react-x/no-missing-key: elements with a spread attribute are no longer reported as missing key, and TypeScript-wrapped iterator callbacks are unwrapped before checking. (#​2086, #​2088)
  • react-x/no-nested-component-definitions: array pattern element defaults and memo propsAreEqual comparators are no longer reported as nested components; optional-chained createElement returns are recognized. (#​2084)
  • react-x/no-unstable-context-value and react-x/no-unstable-default-props: shadowed Boolean(), String(), and Number() calls are no longer reported. (#​2089)
  • react-x/no-unused-class-component-members: statically resolvable computed member reads and destructuring are counted as usages. (#​2088)
  • react-x/refs: non-null guards whose terminating branch is a try statement, an all-terminating switch with a default clause, or an all-terminating while (true)/for (;;)/do...while loop are now recognized, so ref writes reached only when the ref is null are no longer reported. (#​2093, #​2109)
  • react-x/set-state-in-effect: TypeScript-wrapped setups are resolved; zero-argument setters called directly in the setup are reported; timer or event callbacks nested in useCallback/useEffectEvent are no longer treated as synchronous setters; every possible setter is reported when the callee may resolve to more than one; the ref-derived exemption applies to any argument position of a custom state hook's setter; ref-derived early-return guards gate the following statements inside try/switch/bare blocks and loop bodies or update clauses; ref provenance follows IIFEs; nested and outer effect setups are analyzed independently; and setter calls reached through the same effect-side trigger are reported once per setter name. (#​2075, #​2082, #​2083)
  • react-x/static-components: the render-boundary check now requires that at least one declaration of the component binding lives inside a render body, instead of only checking the first declaration. (#​2110)
  • react-x/static-components: static components wrapped by useMemo or useCallback (ex: useMemo(() => External, [])) are no longer reported; the memoized value is traced instead of the hook call itself. (#​2113, closes #​1762) Thanks to @​itisrmk!
  • react-x/use-state: calls in computed object property keys and JSX subtrees are now detected by the lazy-initialization check. (#​2080)
  • react-jsx/no-children-prop-with-children: children supplied through a statically resolvable computed key in a createElement props object is now detected. (#​2086)
  • react-jsx/no-children-prop: children supplied through a statically resolvable computed key in a createElement props object is now detected, and the suggestion to move children into element content is no longer offered when a following spread attribute could override it. (#​2086, #​2102)
  • react-jsx/no-leaked-semicolon: leaked semicolons between a JSX child and its parent's closing tag on the same line are now detected. (#​2102)
  • react-jsx/no-useless-fragment: fragments with a spread attribute are no longer reported, and lone-CR whitespace, including &#&#8203;13;, is treated as formatting padding like LF and CRLF. (#​2086, #​2092)
  • react-dom/no-dangerously-set-innerhtml-with-children: empty expression containers and comment-only children no longer count as children; lone-CR whitespace, including &#&#8203;13;, no longer counts either. (#​2086, #​2092)
  • react-dom/no-hydrate and react-dom/no-render: autofixes now skip calls with extra or spread arguments and calls whose return values are used, and no longer prepend the new import at the top of the file — existing imports are reused, duplicates are skipped, and new imports are placed after file-level directives, header comments, and existing imports. (#​2103, #​2104)
  • react-dom/no-script-url: namespaced attributes such as xlink:href are now checked for javascript: URLs. (#​2086)
  • react-dom/no-unsafe-iframe-sandbox: sandbox permissions are matched as whole whitespace-separated tokens, fixing false positives like sandbox="not-allow-scripts". (#​2112)
  • react-dom/no-unsafe-target-blank: the suggestion for a missing rel attribute now inserts it after the last JSX attribute, so a spread attribute cannot override the suggested value. (#​2086)
  • react-dom/no-use-form-state: autofix-added imports now reuse existing imports, avoid duplicates, and follow file-level directives, header comments, and existing imports. (#​2104)
  • react-dom/no-void-elements-with-children: comment-only/empty containers, newline-only formatting whitespace, and lone-CR whitespace, including &#&#8203;13;, no longer count as children. (#​2086, #​2092)
  • react-web-api/no-leaked-event-listener: dot access and static computed access (including simple template-literal keys) now match as the same property; optional-chained listeners, event types, and receivers pair with their cleanup; string-literal and template-literal option keys are recognized; cyclic signal alias chains no longer recurse forever; and function-parameter callees are no longer mistaken for the enclosing function. (#​2085, #​2092, #​2093, #​2100)
  • react-web-api/no-leaked-fetch: signal option keys written as string literals or simple template literals are recognized. (#​2093)
  • react-web-api/no-leaked-intersection-observer and react-web-api/no-leaked-resize-observer: observe(...) and unobserve(...) now pair on optional-chained elements. (#​2093)
  • react-debug/function-component: only the first argument of memo/forwardRef is treated as the wrapped component; propsAreEqual comparators returning JSX are no longer reported, and functions in that position no longer inherit the surrounding binding or wrapper flags. Array pattern element defaults are no longer reported, and optional-chained createElement returns are recognized. (#​2084)
🪄 Improvements
  • Added fast-path text checks so rules skip AST traversal when their target term is absent from the file. (#​2088)

    Affected rules:

    • react-x/no-children-count
    • react-x/no-children-for-each
    • react-x/no-children-map
    • react-x/no-children-only
    • react-x/no-children-to-array
    • react-x/no-clone-element
    • react-x/no-direct-mutation-state
    • react-x/no-implicit-children
    • react-x/no-implicit-key
    • react-x/no-implicit-ref
    • react-x/no-nested-lazy-component-declarations
    • react-x/no-unused-class-component-members
  • JSX and createElement rules no longer resolve spread props, since a spread's contents are unknown; only direct attributes and properties are inspected. (#​2086)

    Affected rules:

    • react-x/no-missing-key
    • react-jsx/no-children-prop
    • react-jsx/no-children-prop-with-children
    • react-jsx/no-useless-fragment
    • react-dom/no-dangerously-set-innerhtml
    • react-dom/no-dangerously-set-innerhtml-with-children
    • react-dom/no-missing-button-type
    • react-dom/no-missing-iframe-sandbox
    • react-dom/no-string-style-prop
    • react-dom/no-unsafe-iframe-sandbox
    • react-dom/no-unsafe-target-blank
    • react-dom/no-void-elements-with-children
  • react-x/no-unknown-property: attribute-tag, DOM-property, and standard-name lookups are cached per React version and resolved lazily. (#​2086)

  • react-x/set-state-in-effect and react-x/set-state-in-render: setters are recognized only as the second element of a useState array destructuring; tuple-index access and object-pattern numeric keys are no longer detected. (#​2075)

📝 Documentation
  • Added a TanStack Redact example and updated the website's community projects list. (#​2079)
  • Added known-issues references for eslint-plugin-react-jsx (#​2102), eslint-plugin-react-dom (#​2103), eslint-plugin-react-web-api, and eslint-plugin-react-x, and removed their next-step sections.
  • Documented known limitations and workarounds for react-jsx/no-comment-textnodes, react-jsx/no-key-after-spread, and react-jsx/no-leaked-dollar. (#​2102)
  • Synced the migration tables with rule features and updated the configuration and third-party plugin docs. (#​2106)
  • Synced the website recipe snippets with the hardened sample rules, and corrected the noExplicitSpreadProps recipe to state that it provides no autofix. (#​2089, #​2107)
  • Updated the FAQ, glossary, examples pages, the contributing guide's monorepo architecture diagram and package/example listings, and the term-based rule implementation patterns.
🏗️ Internal
  • @eslint-react/ast, @eslint-react/core, and @local/testkit: added tests for AST tree types, core semantic interfaces, and type utilities.
  • @eslint-react/ast: added the Collect and Analyze namespaces and Traverse.simpleTraverse; Analyze.isUnconditionallyTerminating now handles try statements, terminating switch statements with a default clause, and terminating while (true)/for (;;)/do...while loops; Compare.isEqual now compares ChainExpression, regex literals, and member computed/optional flags; Collect now traverses for initializers and updates; renamed Check.isConditional to Check.isConditionalOrLoop; added Check.isArrayPatternElementDefault, Check.isObjectPatternElementDefault, Check.isLoopStatement, and Extract.getJSXName; improved private identifier handling; removed the general-purpose Extract.getMemberChain, Extract.getPropertyName, Extract.findProperty, and Extract.getAssignmentTargets helpers in favor of resolveAssignmentTargets from @eslint-react/var and rule-local traversal. (#​2080, #​2083, #​2084, #​2086, #​2092, #​2093, #​2099, #​2100)
  • @eslint-react/core: moved the createElement helpers to @eslint-react/jsx; component detection now checks wrapper argument positions and unwraps chain expressions; improved render-method detection and qualified type names; narrowed the accepted node types of hook/component detection helpers. (#​2075, #​2077, #​2084, #​2099)
  • @eslint-react/var: added resolveOriginChain, isProvenanceEqual, hasDefault, and resolveAssignmentTargets; expanded resolveObjectType and createImportLookup, which now exposes isModuleBinding instead of hasNamespace; made isValueEqual identity-only (use isProvenanceEqual for structural provenance); and removed resolveBindingTarget/BindingTarget, with binding targets now unwrapped inline. (#​2085, #​2086, #​2088, #​2100)
  • @local/samples: hardened the sample rules. (#​2107)
  • @local/testkit: added a verifyAndFix helper for testing rules with autofixes. (#​2078)
  • Bumped dependencies across the workspace, including eslint to 10.14.0, typescript-eslint to 8.72.1, next to 16.4.5, vitest to 5.1.0, tsdown to 0.23.7, nx to 24.0.4, oxlint to 1.91.0, vite to 8.3.6, effect to 4.1.2, and the fumadocs packages to 16.18.0.
  • Collapsed multi-line expressions in react-x/static-components origins; no behavioral changes.
  • Enforced a 1-day dependency maturity period; served README assets from the jsDelivr CDN; restricted website deployments to stable releases via a Vercel deploy hook; refactored the publish workflow trigger and pinned zizmor through its official action.
  • Removed the ko-fi sponsorship and funding configuration.
  • Removed the now-unused @typescript-eslint/typescript-estree dependency from @eslint-react/ast, @eslint-react/core, @eslint-react/var, and eslint-plugin-react-x. (#​2080)
  • Removed the unused inlinedDependencies field from the monorepo package configuration.
  • Unified test language options and reorganized the test harness: tsconfig fixtures replace the per-JSX-emit tester factories, and untyped parsing disables typescript-estree's single-run inference. (#​2105)
  • Unwrapped multi-line comments to single lines across packages, plugins, and scripts; no behavioral changes.
New Contributors

Full Changelog: Rel1cx/eslint-react@v5.28.8...v5.30.0

microsoft/playwright (@​playwright/test)

v1.65.1

Compare Source

Bug Fixes
  • #​43936 [Regression]: decorated class with a static field fails to load in 1.65 ("_initClass is not a function") with useDefineForClassFields: false
  • #​43934 [Bug]: Test locations are one column off under Bun 1.4.4+
Browser Versions
  • Chromium 159.0.8154.6
  • Mozilla Firefox 159.0
  • WebKit 27.2

v1.65.0

Compare Source

🥟 Run tests with Bun

The test runner now runs under Bun. Bun transpiles your TypeScript test files itself, so Playwright does not use Babel or its compilation cache. Pass the --bun flag, because without it bunx playwright test runs on Node.js:

bunx --bun playwright test

Our CI runs the test runner tests under Bun 1.4.3 on Linux. Some features work differently under Bun:

  • There is no watch mode. UI mode does not run tests again when files change, and --only-changed does not follow imports.
  • Bun loads modules itself, so --tsconfig and the JSX options in tsconfig.json have no effect, and custom ESM loaders are not supported.
  • Stack traces do not include async frames, and API names do not include the class name: click instead of locator.click. This changes some step locations, step titles and error messages.
  • Console output of a test does not get into the trace and UI mode.

🚨 Reports with only failures

New failures reporter prints failures and successful retries as they occur, followed by a summary, without progress output.

New onlyFailures option of the HTML, JSON and JUnit reporters keeps only tests with unexpected outcomes, flaky tests and interrupted tests:

// playwright.config.ts
import { defineConfig } from '@playwright/test';

export default defineConfig({
  reporter: [
    ['failures'],
    ['html', { onlyFailures: true }],
  ],
});

🎯 Test runner

  • New built-in -exclusive- test lock runs a test only when no other tests are running. All other tests continue to run in parallel with each other:

    test('restart the server', { lock: '-exclusive-' }, async () => {
      // No other test runs while this one is running.
    });
  • test.skip(), test.fixme(), test.fail() and test.slow() now accept only a description. It is recorded in the test annotation:

    test('upload a file', async ({ page }) => {
      test.skip('Not implemented yet');
    });
  • New PLAYWRIGHT_TRANSFORM_CACHE_DIR environment variable sets the directory for transpiled test files, for example on a Linux machine shared with other users.

New APIs

Notable Changes ⚠️

  • TypeScript class fields now follow useDefineForClassFields from your tsconfig.json, the same as tsc. It is enabled for ES2022 and later targets, and when target is not specified. A field initializer that reads a constructor parameter property now fails, because the initializer runs first:

    class LoginPage {
      // TypeError: Cannot read properties of undefined (reading 'getByRole')
      readonly submit = this.page.getByRole('button', { name: 'Submit' });
    
      constructor(private readonly page: Page) {}
    }

    Move the initialization to the constructor, or set "useDefineForClassFields": false in your tsconfig.json.

  • Actions such as locator.click(), locator.check(), locator.tap(), locator.fill(), locator.clear() and locator.selectOption() now wait for the element to be not inert. An action on an element with the inert attribute, or inside such an element, now times out if the element stays inert.

  • A sharded run now fails with "No tests found" when no tests match across all shards. Pass --pass-with-no-tests to allow this. An empty shard still passes when other shards have tests.

  • Cookie matching now follows RFC 6265. With a URL, browserContext.cookies() and apiRequestContext.cookies() no longer return host-only cookies for subdomains or Path=/api cookies for /apiv2, and a Path=/foo/ cookie does not match /foo. APIRequestContext sends a cookie without a name as Cookie: x instead of Cookie: =x, and stores Set-Cookie: token as a cookie without a name.

  • Proxy credentials are no longer sent to websites. The credentials in the proxy option now answer only proxy challenges. To authenticate on a website, use httpCredentials.

  • Text that the browser does not render, such as text that is not assigned to a slot or text directly inside a closed <details>, is no longer part of accessible names and aria snapshots. This can change the results of page.getByRole() with a name, locator.ariaSnapshot() and expect(locator).toMatchAriaSnapshot().

  • String and URLSearchParams values of the params option in APIRequestContext requests are now appended to the query that the URL already has, instead of replacing it.

  • .css, .less and .scss imports in test files now load as empty modules instead of being removed, so the imported file must exist.

  • The blob reporter again deletes the content of its output directory before it writes the report. Playwright 1.64 kept reports with other names.

  • Test locations of imported calls such as test( in CommonJS output now point to the start of the callee, for example a.spec.ts:3:7 instead of a.spec.ts:3:11. This is the same as in ESM.

Announcements

  • ⚠️ Playwright no longer tests on Node.js 20. Use Node.js 22, 24 or 26, as listed in the system requirements.
  • 🐳 Docker images now include Node.js 26 instead of Node.js 24, and the latest patch of Chromium on the same branch.

Browser Versions

  • Chromium 158.0.8127.18
  • Mozilla Firefox 159.0
  • WebKit 27.2

This version was also tested against the following stable channels:

  • Google Chrome 157
  • Microsoft Edge 156
testing-library/user-event (@​testing-library/user-event)

v14.6.12

Compare Source

Bug Fixes

v14.6.11

Compare Source

Bug Fixes

v14.6.10

Compare Source

Bug Fixes

v14.6.9

Compare Source

Bug Fixes
vitejs/vite-plugin-react (@​vitejs/plugin-react)

v6.3.0

Compare Source

Make reactCompilerPreset work with @rolldown/plugin-babel's parallel option (#​1549)

reactCompilerPreset now refers to its Babel preset by module path instead of by function, so it can be sent to worker threads.

eslint/eslint (eslint)

v10.15.0

Compare Source

Features

  • ec52157 feat: check proto and assignment targets in func-names (#​21521) (Lê Văn Xuân Hoàn)
  • 34a8b1b feat: recognize string and computed keys in accessor-pairs descriptors (#​21519) (Lê Văn Xuân Hoàn)
  • 663c825 feat: handle TS type assertions in no-invalid-this (#​21464) (Valentin)
  • 4941015 feat: check individual specifier importKind in no-shadow (#​21518) (Lê Văn Xuân Hoàn)
  • 17f17cd feat: update error location to head for default-case (#​21469) (Tanuj Kanti)

Bug Fixes

Documentation

  • 16eb1d9 docs: remove Contributor Pool reference (#​21539) (Nicholas C. Zakas)
  • e368730 docs: discourage non-serializable values in rule options (#​21487) (Vitalii Maslianok)
  • 0146008 docs: revamp code path analysis docs (#​21423) (xbinaryx)
  • aeb2267 docs: revise AI acknowledgment options in templates (#​21489) (lumir)
  • e47a477 docs: Update README (GitHub Actions Bot)
  • 11c66ba docs: fix typo in custom rules documentation (#​21472) (Pixel)

Chores

ArnaudBarre/eslint-plugin-react-refresh (eslint-plugin-react-refresh)

v0.5.8

[Compare Source](https://redirect.github.com/ArnaudBarre/eslint-plugin-react-refresh/compare/v0.5.7

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (in timezone Europe/Amsterdam)

  • Branch creation
    • Between 12:00 AM and 07:59 AM, only on Saturday (* 0-7 * * 6)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

@coderabbitai

coderabbitai Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 2d308790-3022-4056-81b3-80ac6a715a42

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

Share

@renovate
renovate Bot force-pushed the renovate/all-non-major branch 2 times, most recently from 1f7c57f to 4b18b4c Compare November 18, 2026 19:43
@renovate renovate Bot changed the title chore(deps): update all non-major dependencies [automerge] build(deps): update all non-major dependencies [automerge] Nov 18, 2026
@renovate
renovate Bot force-pushed the renovate/all-non-major branch 2 times, most recently from 4b577bc to e631155 Compare November 19, 2026 06:42
@renovate
renovate Bot force-pushed the renovate/all-non-major branch from e631155 to f4b06e2 Compare November 19, 2026 19:02
@renovate
renovate Bot merged commit cd32c55 into main Nov 20, 2026
28 checks passed
@renovate
renovate Bot deleted the renovate/all-non-major branch November 20, 2026 05:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants