chore(deps): update all non-major dependencies #1293

renovate · 2025-10-27T01:49:00Z

This PR contains the following updates:

Package	Change	Age	Confidence
@biomejs/biome (source)	`^2.2.6` -> `^2.3.1`
@microsoft/api-extractor (source)	`^7.53.1` -> `^7.53.3`
@reduxjs/toolkit (source)	`^2.9.1` -> `^2.9.2`
@shikijs/transformers (source)	`^3.13.0` -> `^3.14.0`
@storybook/addon-docs (source)	`^9.1.13` -> `^9.1.15`
@storybook/addon-onboarding (source)	`^9.1.13` -> `^9.1.15`
@storybook/react (source)	`^9.1.13` -> `^9.1.15`
@storybook/vue3 (source)	`^9.1.13` -> `^9.1.15`
@tailwindcss/postcss (source)	`^4.1.15` -> `^4.1.16`
@types/express (source)	`^5.0.3` -> `^5.0.4`
@typescript/native-preview (source)	`7.0.0-dev.20251021.1` -> `7.0.0-dev.20251026.1`
magic-string	`^0.30.19` -> `^0.30.21`
nx (source)	`^21.6.5` -> `^21.6.6`
pnpm (source)	`10.18.0` -> `10.19.0`
pnpm (source)	`>=10.18.0` -> `>=10.19.0`
rslib (source)	`0.16.0` -> `0.16.1`
storybook (source)	`^9.1.13` -> `^9.1.15`
tailwindcss (source)	`^4.1.15` -> `^4.1.16`
vue-tsc (source)	`^3.1.1` -> `^3.1.2`

Release Notes

biomejs/biome (@biomejs/biome)

`v2.3.1`

Compare Source

Patch Changes

#7840 72afdfa Thanks @ematipico! - Fixed #7838, which caused the new --css-parse-* arguments not being recognised by the ci command.
#7789 d5b416e Thanks @fronterior! - Fixed the LSP method workspace/didChangeWorkspaceFolders to perform incremental updates instead of replacing the entire folder list.
#7852 bd254c7 Thanks @dyc3! - Fixed #7843: The CSS parser, when tailwindDirectives is enabled, correctly parses --*: initial;.
#7872 0fe13fe Thanks @dyc3! - Fixed #7861: The HTML parser will now accept Svelte attribute shorthand syntax in .svelte files.
#7866 7b2600b Thanks @dyc3! - Fixed #7860: The css parser, with tailwindDirectives enabled, will now accept @plugin options.
#7853 fe90c78 Thanks @dyc3! - Fixed #7848: The css parser with tailwindDirectives enabled will now correctly parse tailwind's source exclude syntax: @source not "foo.css";
#7878 c9f7fe5 Thanks @ematipico! - Fixed #7857: Biome now parses <script> tags as TypeScript when analysing .astro files.
#7867 b42b718 Thanks @smorimoto! - Fixed incorrect option name in HTML parser error message.

The error message for disabled text expressions incorrectly referred
to the html.parser.textExpression option, which does not exist.
Updated it to reference the correct html.parser.interpolation option.

`v2.3.0`

Compare Source

Minor Changes

#7263 a3e3369 Thanks @arendjr! - Biome's resolver now supports baseUrl if specified in tsconfig.json.

Example

Given the following file structure:

tsconfig.json

{ "compilerOptions": { "baseUrl": "./src" } }

src/foo.ts

export function foo() {}

In this scenario, import { foo } from "foo"; should work regardless of the
location of the file containing the import statement.

Fixes #6432.

#7745 6fcbc07 Thanks @dyc3! - Added ignore option to noUnknownAtRules. If an unknown at-rule matches any of the items provided in ignore, a diagnostic won't be emitted.
#7753 63cb7ff Thanks @ematipico! - Enhanced the init command. The init command now checks if the existing project contains known ignore files and known generated folders.

If Biome finds .gitignore or .ignore files, it will add the following configuration to biome.json:
```
{ + "vcs": { + "enabled": true, + "clientKind": "git", + "useIgnoreFile": true + } }
```
If Biome finds a dist/ folder, it will exclude it automatically using the double-exclude syntax:
```
{ + "files": { + "includes": ["**", "!!**/dist"] + } }
```
#7548 85d3a3a Thanks @siketyan! - The rules in a domain are no longer enabled automatically by the installed dependencies unless the rule is recommended.

#7723 d3aac63 Thanks @ematipico! - Added --css-parse-css-modules CLI flag to control whether CSS Modules syntax is enabled.

You can now enable or disable CSS Modules parsing directly from the command line:

biome check --css-parse-css-modules=true file.module.css biome format --css-parse-css-modules=true file.module.css biome lint --css-parse-css-modules=true file.module.css biome ci --css-parse-css-modules=true file.module.css

#7723 d3aac63 Thanks @ematipico! - Added --css-parse-tailwind-directives CLI flag to control whether Tailwind CSS 4.0 directives and functions are enabled.

You can now enable or disable Tailwind CSS 4.0 directive parsing directly from the command line:
```
biome check --css-parse-tailwind-directives=true file.css biome format --css-parse-tailwind-directives=true file.css biome lint --css-parse-tailwind-directives=true file.css biome ci --css-parse-tailwind-directives=true file.css
```
#7330 272632f Thanks @ematipico! - Updated the formatting of .svelte and .vue files. Now the indentation of the JavaScript blocks matches Prettier's:
```
<script> - import Component from "./Component" + import Component from "./Component" </script>
```
#7333 de0d2d6 Thanks @dyc3! - Implemented the indentScriptAndStyle option for vue and svelte files, with the default set to false to match Prettier's vueIndentScriptAndStyle option. When enabled, this option indents the content within <script> and <style> tags to align with the surrounding HTML structure.

It can be enabled with this configuration:
```
{ "html": { "formatter": { "indentScriptAndStyle": true } } }
```
Which will format this code to:
```
<script> import Component from "./Component.vue"; </script>
```
#7359 ebbddc4 Thanks @arendjr! - Deprecated the option files.experimentalScannerIgnores in favour of force-ignore syntax in files.includes.

files.includes supports ignoring files by prefixing globs with an exclamation mark (!). With this change, it also supports force-ignoring globs by prefixing them with a double exclamation mark (!!).

The effect of force-ignoring is that the scanner will not index files matching the glob, even in project mode, even if those files are imported by other files, and even if they are files that receive special treatment by Biome, such as nested biome.json files.

Example

Let's take the following configuration:

{ "files": { "includes": [ "**", "!**/generated", "!!**/dist", "fixtures/example/dist/*.js" ] }, "linter": { "domains": { "project": "all" } } }

This configuration achieves the following:

Because the project domain is enabled, all supported files in the project are indexed and processed by the linter, except:
Files inside a generated folder are not processed by the linter, but they will get indexed if a file outside a generated folder imports them.
Files inside a dist folder are never indexed nor processed, not even if they are imported for any purpose, except:
When the dist folder is inside fixtures/example/, its .js files do get both indexed and processed.

In general, we now recommend using the force-ignore syntax for any folders that contain output files, such as build/ and dist/. For such folders, it is highly unlikely that indexing has any useful benefits. For folders containing generated files, you may wish to use the regular ignore syntax so that type information can still be extracted from the files.

experimentalScannerIgnores will continue to work for now, but you'll see a deprecation warning if you still use it.

Run the biome migrate --write command to automatically update the configuration file.

#7698 3b6f5e3 Thanks @ematipico! - Added a new reporter named rdjson. This reporter prints diagnostics following the RDJSON format:

The following command:

biome check --reporter=rdjson

Will emit diagnostics in the following format:

{ "source": { "name": "Biome", "url": "https://biomejs.dev" }, "diagnostics": [ { "code": { "url": "https://biomejs.dev/linter/rules/no-unused-imports", "value": "lint/correctness/noUnusedImports" }, "location": { "path": "index.ts", "range": { "end": { "column": 11, "line": 0 }, "start": { "column": 7, "line": 0 } } }, "message": "This import is unused." }, { "code": { "url": "https://biomejs.dev/linter/rules/no-unused-imports", "value": "lint/correctness/noUnusedImports" }, "location": { "path": "index.ts", "range": { "end": { "column": 10, "line": 1 }, "start": { "column": 9, "line": 1 } } }, "message": "Several of these imports are unused." } ] }

#7719 188a767 Thanks @cadunass! - The formatWithErrors option can now be set via CLI using the --format-with-errors flag.

This flag was previously only available in the configuration file. It allows formatting to proceed on files with syntax errors, which is useful during development when you want to auto-format code while fixing syntax issues.

Example

biome format --format-with-errors=true --write file.js

#7723 d3aac63 Thanks @ematipico! - Added --json-parse-allow-comments CLI flag to control whether comments are allowed in JSON files.

You can now enable or disable comment parsing in JSON files directly from the command line:
```
biome check --json-parse-allow-comments=true file.json biome format --json-parse-allow-comments=true file.json biome lint --json-parse-allow-comments=true file.json biome ci --json-parse-allow-comments=true file.json
```
#7723 d3aac63 Thanks @ematipico! - Added --json-parse-allow-trailing-commas CLI flag to control whether trailing commas are allowed in JSON files.

You can now enable or disable trailing comma parsing in JSON files directly from the command line:
```
biome check --json-parse-allow-trailing-commas=true file.json biome format --json-parse-allow-trailing-commas=true file.json biome lint --json-parse-allow-trailing-commas=true file.json biome ci --json-parse-allow-trailing-commas=true file.json
```
#7758 cea002f Thanks @ematipico! - Promoted new lint rules:
- Promoted noNonNullAssertedOptionalChain to the suspicious group
- Promoted useReactFunctionComponents to the style group
- Promoted useImageSize to the correctness group
- Promoted useConsistentTypeDefinitions to the style group
- Promoted useQwikClasslist to the correctness group
- Promoted noSecrets to the security group
Removed the lint rule useAnchorHref, because its use case is covered by useValidAnchor.

#6356 296627d Thanks @wrick17! - Added the new checkstyle reporter. When --reporter=checkstyle is passed to the CLI, Biome will emit diagnostics for Checkstyle format:

<?xml version="1.0" encoding="utf-8"?> <checkstyle version="4.3"> <file name="index.ts"> <error line="1" column="8" severity="warning" message="This import is unused." source="lint/correctness/noUnusedImports" /> <error line="2" column="10" severity="warning" message="Several of these imports are unused." source="lint/correctness/noUnusedImports" /> <error line="8" column="5" severity="warning" message="This variable f is unused." source="lint/correctness/noUnusedVariables" /> <error line="9" column="7" severity="warning" message="This variable f is unused." source="lint/correctness/noUnusedVariables" /> <error line="1" column="1" severity="error" message="The imports and exports are not sorted." source="assist/source/organizeImports" /> <error line="4" column="3" severity="error" message="Using == may be unsafe if you are relying on type coercion." source="lint/suspicious/noDoubleEquals" /> <error line="6" column="1" severity="error" message="This is an unexpected use of the debugger statement." source="lint/suspicious/noDebugger" /> <error line="8" column="5" severity="error" message="This variable implicitly has the any type." source="lint/suspicious/noImplicitAnyLet" /> <error line="9" column="7" severity="error" message="This variable implicitly has the any type." source="lint/suspicious/noImplicitAnyLet" /> <error line="2" column="10" severity="error" message="Shouldn&apos;t redeclare &apos;z&apos;. Consider to delete it or rename it." source="lint/suspicious/noRedeclare" /> <error line="9" column="7" severity="error" message="Shouldn&apos;t redeclare &apos;f&apos;. Consider to delete it or rename it." source="lint/suspicious/noRedeclare" /> <error line="0" column="0" severity="error" message="Formatter would have printed the following content:" source="format" /> </file> <file name="main.ts"> <error line="1" column="8" severity="warning" message="This import is unused." source="lint/correctness/noUnusedImports" /> <error line="2" column="10" severity="warning" message="Several of these imports are unused." source="lint/correctness/noUnusedImports" /> <error line="8" column="5" severity="warning" message="This variable f is unused." source="lint/correctness/noUnusedVariables" /> <error line="9" column="7" severity="warning" message="This variable f is unused." source="lint/correctness/noUnusedVariables" /> <error line="1" column="1" severity="error" message="The imports and exports are not sorted." source="assist/source/organizeImports" /> <error line="4" column="3" severity="error" message="Using == may be unsafe if you are relying on type coercion." source="lint/suspicious/noDoubleEquals" /> <error line="6" column="1" severity="error" message="This is an unexpected use of the debugger statement." source="lint/suspicious/noDebugger" /> <error line="8" column="5" severity="error" message="This variable implicitly has the any type." source="lint/suspicious/noImplicitAnyLet" /> <error line="9" column="7" severity="error" message="This variable implicitly has the any type." source="lint/suspicious/noImplicitAnyLet" /> <error line="2" column="10" severity="error" message="Shouldn&apos;t redeclare &apos;z&apos;. Consider to delete it or rename it." source="lint/suspicious/noRedeclare" /> <error line="9" column="7" severity="error" message="Shouldn&apos;t redeclare &apos;f&apos;. Consider to delete it or rename it." source="lint/suspicious/noRedeclare" /> <error line="0" column="0" severity="error" message="Formatter would have printed the following content:" source="format" /> </file> </checkstyle>

#7488 b13e524 Thanks @kpapa05! - Added "@rbxts/react" as an alias for "react" for handling the reactClassic jsxRuntime.
#7536 0bccd34 Thanks @TheAlexLichter! - Added .oxlintrc.json to well-known files.
#7548 85d3a3a Thanks @siketyan! - The following rules are now a part of the react domain, and they won't be enabled automatically unless you enabled the domain, or Biome detects react as a dependency of your closest package.json:
- lint/correctness/noChildrenProp (recommended)
- lint/correctness/noReactPropAssignments
- lint/security/noDangerouslySetInnerHtml (recommended)
- lint/security/noDangerouslySetInnerHtmlWithChildren (recommended)
- lint/style/useComponentExportOnlyModules
- lint/suspicious/noArrayIndexKey (recommended)
#7667 480909a Thanks @ematipico! - Added the ability to show severity Information diagnostics in reporter outputs.

If one or more rules are triggered, and they are configured to emit an Information diagnostic, now they're counted in the final output:
```
Checked 1 file in <TIME>. No fixes applied. Found 1 info.
```
#7702 28e8860 Thanks @ematipico! - Added linting and assist support for .html files, with addition of two new configurations:
- html.linter.enabled
- html.assist.enabled
The HTML linter, in this release, only contains the rule noHeaderScope. More rules will be released in the upcoming releases.
#7164 f66b0c5 Thanks @dyc3! - Added a new CSS parser option tailwindDirectives. Enabling this option will allow all of Tailwind v4's syntax additions to be parsed and formatted by Biome.

You can enable this by setting css.parser.tailwindDirectives to true in your Biome configuration.
```
{ "css": { "parser": { "tailwindDirectives": true } } }
```
#7669 6ed4d16 Thanks @barklund! - React 19.2 support is now supported in Biome:
- Treats useEffectEvent like useRef in useExhaustiveDependencies
- Added <Activity /> to known React APIs.
#7702 28e8860 Thanks @ematipico! - Added experimental full support for HTML, Vue, Svelte and Astro files. In this release, the HTML parser
has been enhanced, and it's now able to parse .vue, .svelte and .astro files.

This means that now Biome is able to lint and format the JavaScript (TypeScript), HTML and CSS code that is contained in these files.

Now that the main architecture is stable and working, in the upcoming patches and minors we will also fix possible inaccuracies and edge cases coming from existing lint rules, such as noUnusedVariables inside <script> blocks or frontmatter.

The support is considered experimental because there might be cases that aren't fine-parsed yet, hence causing possible inaccuracies when it comes to formatting and linting.
#7599 09445c8 Thanks @anaisbetts! - #### lineEnding has a new option auto

The option lineEnding now has a variant called auto to match the operating system's expected
line-ending style: on Windows, this will be CRLF (\r\n), and on macOS / Linux, this will
be LF (\n).

This allows for cross-platform projects that use Biome not to have to
force one option or the other, which aligns better with Git's default behavior
on these platforms.

Example usage:
```
{ "formatter": { "lineEnding": "auto" } }
```
```
biome format --line-ending auto
```
#7392 e4feb8e Thanks @ematipico! - Added new capabilities to the CLI arguments --skip and --only, available to the biome lint command.

--skip and --only can now accept domain names; when provided, Biome will run or skip all the rules that belong to a certain domain.

For example, the following command will only run the rules that belong to the next domain:
```
biome lint --only=next
```
Another example, the following command will skip the rules that belong to the project domain:
```
biome lint --skip=project
```
#7702 28e8860 Thanks @ematipico! - Added a new option called html.interpolation. This option enables the parsing of text expressions (or interpolation) in HTML files.

The following file.html will be correctly formatted:
```
 <div> Hello {{ name }}! <p>Your balance is: {{ account.balance }}</p> <button>{{ isLoading ? "Loading..." : "Submit" }}</button> </div>
```
To note that html.interpolation only parses text expressions that are delimited by double curly braces ({{ }}). The content of expressions is parsed as normal text.

Patch Changes

#7712 fcc9b42 Thanks @minht11! - Added new rule useVueDefineMacrosOrder which allows enforcing specific order for Vue compiler macros.

In this example, the rule will suggest moving defineProps before defineEmits:
```
<script lang="ts" setup> const emit = defineEmits(["update"]); const props = defineProps<{ name: string }>(); </script>
```
#7698 3b6f5e3 Thanks @ematipico! - Fixed an issue where the JUnit reporter returned a zero-based location. Now the location returned is one-based.
#7819 ef45056 Thanks @ematipico! - Fixed #7788. Removes some error logging that were emitted when loading possible configuration files.
#7593 e51dd55 Thanks @arendjr! - Fixed an issue with the files.maxSize setting. Previously the setting would always be looked up in the root settings, even in monorepos where a closer biome.json is available. It now correctly uses the nearest configuration.
#7825 ad55b35 Thanks @Conaclos! - Fixed #7798. useNamingConvention no longer panics when it encounters a name that consists of a single dollar sign $ that doesn't match a custom convention.
#7764 93be2ab Thanks @gaauwe! - Fixed #6589: Biome now properly loads extension settings before loading the configuration file when opening a text document in the LSP server.

`v2.2.7`

Compare Source

Patch Changes

#7715 b622425 Thanks @Netail! - Added the nursery rule noEmptySource, disallowing meaningless js, css, json & graphql files to prevent codebase clutter.
#7714 c7e5a14 Thanks @MeGaNeKoS! - Increased the maximum line limit for noExcessiveLinesPerFunction from 255 to 65,535 to better support large JSX/front-end components.
#5868 2db73ae Thanks @bushuai! - Fixed #5856, noRedundantUseStrict now keeps leading trivia
#7756 d665c97 Thanks @ematipico! - Improved the diagnostic message of the rule noDuplicateTestHooks.

microsoft/rushstack (@microsoft/api-extractor)

`v7.53.3`

Compare Source

Fri, 24 Oct 2025 00:13:38 GMT

Version update only

`v7.53.2`

Compare Source

Wed, 22 Oct 2025 00:57:54 GMT

Version update only

reduxjs/redux-toolkit (@reduxjs/toolkit)

`v2.9.2`

Compare Source

This bugfix release fixes a potential internal data leak in SSR environments, improves handling of headers in fetchBaseQuery, improves retry handling for unexpected errors and request aborts, and fixes a longstanding issue with prefetch leaving an unused subscription. We've also shipped a new graphqlRequestBaseQuery release with updated dependencies and better error handling.

Changelog

Internal Subscription Handling

We had a report that a Redux SSR app had internal subscription data showing up across different requests. After investigation, this was a bug introduced by the recent RTKQ perf optimizations, where the internal subscription fields were hoisted outside of the middleware setup and into createApi itself. This meant they existed outside of the per-store-instance lifecycle. We've reworked the logic to ensure the data is per-store again. We also fixed another issue that miscalculated when there was an active request while checking for cache entry cleanup.

Note that no actual app data was leaked in this case, just the internal subscription IDs that RTKQ uses in its own middleware to track the existence of subscriptions per cache entry.

`fetchBaseQuery` Headers

We've updated fetchBaseQuery to avoid setting content-type in cases where a non-JSONifiable value like FormData is being passed as the request body, so that the browser can set that content type itself. It also now sets the accept header based on the selected responseHandler (JSON or text).

`retry` Behavior and Cleanup

The retry util now respects the maxRetries option when catching unknown errors in addition to the existing known errors logic. It also now checks the request's AbortSignal and will stop retrying if aborted.

In conjunction with that, dispatching resetApiState will now abort all in-flight requests.

The prefetch util and usePrefetch hook had a long-standing issue where they would create a subscription for a cache entry, but there was no way to clean up that subscription. This meant that the cache entry was effectively permanent. They now initiate the request without adding a subscription. This will fetch the cache entry and leave it in the store for the keepUnusedDataFor period as intended, giving your app time to actually subscribe to the value (such as prefetching the cache entry in a route handler, and then subscribing in a component).

`graphqlRequestBaseQuery`

We've published @rtk-query/graphql-request-base-query v2.3.2, which updates the graphql-request dep to ^7. We also fixed an issue where the error handling rethrew unknown errors - it now returns {error} as a base query is supposed to.

What's Changed

Fix potential subscription leakage in SSR environments by @markerikson in #5111
Improve fetchBaseQuery default headers handling by @markerikson in #5112
Respect maxRetries for unexpected errors by @markerikson in #5113
fix: update graphql-request dependency to include version ^7.0.0 by @eyesfocus in #4987
Add retry abort handling and abort on resetApiState by @markerikson in #5114
Don't create subscriptions for prefetch calls by @markerikson in #5116

Full Changelog: reduxjs/redux-toolkit@v2.9.1...v2.9.2

shikijs/shiki (@shikijs/transformers)

`v3.14.0`

Compare Source

🚀 Features

Update grammars and themes - by @antfu (26372)

🐞 Bug Fixes

colorized-brackets: Fix default color does not work with colorized-brackets - by @oatmealproblem in #1082 (f4d3f)

View changes on GitHub

storybookjs/storybook (@storybook/addon-docs)

`v9.1.15`

Compare Source

Core: Add preview-first-load telemetry - #32770, thanks @shilman!
Dependencies: Update vite-plugin-storybook-nextjs - #32821, thanks @ndelangen!

`v9.1.14`

Compare Source

storybookjs/storybook (@storybook/addon-onboarding)

`v9.1.15`

Compare Source

9.1.15

Core: Add `preview-first-load` telemetry - #32770, thanks @shilman!
Dependencies: Update `vite-plugin-storybook-nextjs` - #32821, thanks @ndelangen!

`v9.1.14`

Compare Source

9.1.14

NextJS: Add NextJS 16 support - #32791, thanks @yannbf and @ndelangen!
Addon-Vitest: Support Vitest 4 - #32819, thanks @yannbf and @ndelangen!
CSF: Fix `play-fn` tag for methods - #32695, thanks @shilman!

tailwindlabs/tailwindcss (@tailwindcss/postcss)

`v4.1.16`

Compare Source

Fixed

Discard candidates with an empty data type (#19172)
Fix canonicalization of arbitrary variants with attribute selectors (#19176)
Fix invalid colors due to nested & (#19184)
Improve canonicalization for & > :pseudo and & :pseudo arbitrary variants (#19178)

microsoft/typescript-go (@typescript/native-preview)

21.6.6 (2025-10-21)

🩹 Fixes

angular: improve message for unsupported typescript project references (#33148)
angular: ensure ngpackagr tsconfig options set correctly based on version #33081 (#33150, #33081)
angular-rspack: ensure root node_modules included when resolving packages (#33144, #33026)
core: improve db connection initialization and error messages (#33054, #28640, #30856, #32894)
core: prioritize in-progress tasks section visibility in tui (#33053)
core: enhance tui summary output to fix misc issues (#33057)
core: restore migrations used by nx repair (#33124)
core: avoid changing existing project name if a project.json file is added to a project (#33114)
core: do not remove wal files manually for existing databases (#33143)
core: do not print flaky tasks guidance when nx cloud is already enabled (#33149)
core: add wrappers for start and stop agent nx-cloud commands (#33140)
core: revert changes to the db connection initialization (#33156)
graph: prevent content from overflowing in the PDV component (#33120)
linter: install correct deps in eslint convert to flat config generator (#33078)
module-federation: ensure angular rspack module federation supports live reload (#33137)
remix: ensure supported version of vite is used (#33089)
vite: add logic to prevent overwriting generated package.json (#30705, #30312)

❤️ Thank You

Colum Ferry @Coly010
Craigory Coppola @AgentEnder
David Scourfield @daiscog
Jack Hsu [@

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: 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.

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

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

netlify · 2025-10-27T01:50:48Z

✅ Deploy Preview for rslib ready!

Name	Link
🔨 Latest commit	`81b30c6`
🔍 Latest deploy log	https://app.netlify.com/projects/rslib/deploys/68fecf9086665d000878b2c1
😎 Deploy Preview	https://deploy-preview-1293--rslib.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

chore(deps): update all non-major dependencies

81b30c6

chore: update

a3d6d64

Timeless0911 approved these changes Oct 27, 2025

View reviewed changes

Timeless0911 merged commit 3be1979 into main Oct 27, 2025
14 checks passed

Timeless0911 deleted the renovate/all-non-major branch October 27, 2025 06:32

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

chore(deps): update all non-major dependencies #1293

chore(deps): update all non-major dependencies #1293

Uh oh!

renovate bot commented Oct 27, 2025

netlify bot commented Oct 27, 2025

Uh oh!

Labels

2 participants

Uh oh!

chore(deps): update all non-major dependencies #1293

chore(deps): update all non-major dependencies #1293

Uh oh!

Conversation

renovate bot commented Oct 27, 2025

Release Notes

Patch Changes

Minor Changes

Example

Example

Example

Patch Changes

Patch Changes

Changelog

Internal Subscription Handling

fetchBaseQuery Headers

retry Behavior and Cleanup

graphqlRequestBaseQuery

What's Changed

🚀 Features

🐞 Bug Fixes

9.1.15

9.1.14

Fixed

21.6.6 (2025-10-21)

🩹 Fixes

❤️ Thank You

Configuration

netlify bot commented Oct 27, 2025

✅ Deploy Preview for rslib ready!

Uh oh!

Labels

2 participants

`fetchBaseQuery` Headers

`retry` Behavior and Cleanup

`graphqlRequestBaseQuery`