[dependabot]

Bumps the dependencies group with 46 updates in the / directory:

Package	From	To
@changesets/cli	3.0.2	3.0.3
@playwright/test	1.63.0	1.64.1
@types/node	26.5.1	26.6.5
concurrently	10.0.5	10.0.6
i18next	26.4.2	26.4.4
lint-staged	17.5.1	17.6.0
node-gyp	13.0.2	13.1.0
prettier	3.9.6	3.9.10
storybook	10.6.0	10.6.2
turbo	2.10.12	2.11.8
@rjsf/utils	6.10.0	6.11.0
@testing-library/dom	10.4.1	10.4.2
pg	8.23.0	8.23.1
@storybook/addon-docs	10.6.0	10.6.2
@storybook/addon-links	10.6.0	10.6.2
@storybook/react	10.6.0	10.6.2
@storybook/react-vite	10.6.0	10.6.2
@typescript-eslint/eslint-plugin	8.70.0	8.71.2
@typescript-eslint/parser	8.70.0	8.71.2
chalk	6.0.0	6.0.1
eslint	10.10.0	10.12.0
eslint-plugin-jest	29.16.6	29.17.0
eslint-plugin-storybook	10.6.0	10.6.2
jsdom	30.0.1	30.1.2
msw-storybook-addon	3.0.0	3.0.3
tsx	4.23.13	4.23.15
typescript-eslint	8.70.0	8.71.2
rollup	4.63.1	4.64.6
web-tree-sitter	0.27.0	0.27.1
@aws-sdk/client-resource-groups-tagging-api	3.1130.0	3.1151.0
@aws-sdk/client-sts	3.1130.0	3.1151.0
@azure/identity	4.13.2	4.14.0
@google-cloud/resource-manager	7.1.0	7.2.0
@spotify/backstage-plugin-soundcheck-backend	0.31.1	0.33.2
@spotify/backstage-plugin-soundcheck-node	0.16.0	0.16.1
@backstage-community/plugin-tech-radar-backend	1.21.0	1.22.0
@aws-sdk/client-codecommit	3.1130.0	3.1151.0
azure-devops-node-api	17.0.0	17.0.1
@aws-sdk/client-bedrock-runtime	3.1130.0	3.1151.0
@aws-sdk/types	3.974.5	3.974.6
@langchain/aws	1.4.5	1.4.6
@langchain/openai	1.5.12	1.6.2
@langchain/openrouter	0.4.12	0.4.17
@langchain/langgraph	1.4.15	1.5.0
@jest/globals	30.5.1	30.5.2
@langchain/textsplitters	1.0.1	1.0.2

Updates @changesets/cli from 3.0.2 to 3.0.3

Release notes

Sourced from @​changesets/cli's releases.

@​changesets/cli@​3.0.3

Patch Changes

• #2297 3f163da Thanks @​Andarist! - Fixed semver ranges (such as >=1.0.0 <2.0.0) getting cut off (>=2.0.0) when updating internal dependencies.

• #2276 ca9d110 Thanks @​Andarist! - Fixed pnpm 10 compatibility with npm 12 when reading registry information, packing, and publishing packages.

• Updated dependencies [3f163da, bfe9050, e522996]:

  • @​changesets/apply-release-plan@​8.1.1
  • @​changesets/config@​4.0.1

Changelog

Sourced from @​changesets/cli's changelog.

3.0.3

Patch Changes

• #2297 3f163da Thanks @​Andarist! - Fixed semver ranges (such as >=1.0.0 <2.0.0) getting cut off (>=2.0.0) when updating internal dependencies.

• #2276 ca9d110 Thanks @​Andarist! - Fixed pnpm 10 compatibility with npm 12 when reading registry information, packing, and publishing packages.

• Updated dependencies [3f163da, bfe9050, e522996]:

  • @​changesets/apply-release-plan@​8.1.1
  • @​changesets/config@​4.0.1

Commits

• c9269c0 Version Packages (#2291)
• ca9d110 Fix pnpm 10 publishing with npm 12 (#2276)
• 7be7fde Build(deps): Bump the production-dependencies group across 1 directory with 6...
• b430ce0 Move e2e tests to an on-demand workspace (#2275)
• 93314a8 test: add happy path tests for add (#2289)
• d13a39e test: use inline snapshots for publish plan tests (#2284)
• See full diff in compare view

Updates @playwright/test from 1.63.0 to 1.64.1

Release notes

Sourced from @​playwright/test's releases.

v1.64.1

Bug Fixes

• #43247 [Bug]: _electron.launch intermittently loses a packaged app's first window since 1.64.0
• #43242 [Regression]: Chromium 155+ aborts a preflighted cross-origin redirect whenever any route is registered (net::ERR_ABORTED)

v1.64.0

🧰 WebMCP

New page.webmcp and frame.webmcp give access to the tools that a page registers through the experimental WebMCP browser API, so you can test them like any other part of your app:

const browser = await chromium.launch({ args: ['--enable-features=WebMCP'] });
const page = await browser.newPage();
await page.goto('https://example.com');
for (const tool of await page.webmcp.tools())
console.log(tool.name, tool.description);
const result = await page.webmcp.callTool('add', { a: 2, b: 40 });
console.log(result.content[0].text); // "42"

Playwright MCP also supports WebMCP by default, with page-defined tools offered to the agent as webmcp_<tool>. Pass --no-webmcp to opt out.

playwright-cli exposes them as well:

playwright-cli webmcp-list
playwright-cli webmcp-call search_catalog --params '{"query":"cats"}'

🎬 Better videos

Videos can now be recorded at a custom frame rate, and the decorations for actions are styled with plain CSS:

// playwright.config.ts
import { defineConfig } from '@playwright/test';
export default defineConfig({
use: {
video: {
mode: 'on',
size: { width: 1920, height: 1080 },
fps: 60,
show: {
actions: {
style: {
point: 'width: 20px; height: 20px; border-radius: 50%; background: red',
</tr></table>

... (truncated)

Commits

• cfe490d cherry-pick(#43353): docs: release notes for v1.64 Python
• 866cbb8 chore: mark v1.64.1 (#43354)
• 1b29247 cherry-pick(#43250): fix(electron): do not drop windows that have not navigat...
• 632d976 cherry-pick(#43249): fix(chromium): disable AvoidCorsURLLoaderRestartOnRedirect
• 824d0c5 cherry-pick(#43217): chore(dotnet): fix async suffix of optional-arg overload...
• 606ecd8 cherry-pick(#43192): fix(locators): parse locators the way the client API bui...
• e4f872c cherry-pick(#43188): feat(api): expose asLocatorDescription via LocalUtils fo...
• f6a439e cherry-pick(#43189): docs(webmcp): expose WebMCP to all languages
• e2335c3 cherry-pick(#43174): fix(mcp): do not close the browser twice when the client...
• d2a436e cherry-pick(#43163): Revert "fix(blob): do not remove existing reports from o...
• Additional commits viewable in compare view

Updates @types/node from 26.5.1 to 26.6.5

Commits

• See full diff in compare view

Updates concurrently from 10.0.5 to 10.0.6

Release notes

Sourced from concurrently's releases.

v10.0.6

What's Changed

• docs: update issue link to the transferred repo path by @​yzxcj797 in open-cli-tools/concurrently#609
• docs: update API example to ESM by @​Bibin-VR in open-cli-tools/concurrently#611
• fix: skip force-kill logging when no processes remain by @​imshunsuke in open-cli-tools/concurrently#616
• deps: update shell-quote to 1.12.0 by @​Abicodexi and @​Mayvis in open-cli-tools/concurrently#622

New Contributors

• @​yzxcj797 made their first contribution in open-cli-tools/concurrently#609
• @​Bibin-VR made their first contribution in open-cli-tools/concurrently#611
• @​imshunsuke made their first contribution in open-cli-tools/concurrently#616
• @​Abicodexi made their first contribution in open-cli-tools/concurrently#622

Full Changelog: open-cli-tools/concurrently@v10.0.5...v10.0.6

Commits

• d84bab6 10.0.6
• d26574e deps: update shell-quote to 1.12.0 (#622)
• 13bdff1 fix: skip force-kill logging when no processes remain (#616)
• b2580cc docs: update API example to ESM (#611)
• 3159edb docs: update issue link to the transferred repo path (#609)
• See full diff in compare view

Updates i18next from 26.4.2 to 26.4.4

Release notes

Sourced from i18next's releases.

v26.4.4

• fix(security): the nesting regexp no longer backtracks exponentially (ReDoS) on an unclosed $t(. Its repeated group had overlapping alternatives ([^()"']+ inside (?:...)*?, and inside parentheses [^()] also matched quotes), so a string containing $t( without a closing ) made the engine try every way to split the text: about 2x the runtime per extra character, and a ~25 character value hung t() for minutes. With the default config this was reachable through any interpolated value (t('greet', { name: '$t(aaaaaaaaaaaaaaaaaaaaaaaa' })): escaping does not touch $, t or (, and the skipOnVariables check runs the regexp on the interpolated result, so nest: false did not help either. Every alternative now starts with a different character (plain char, ", ' or (), so there is only one way to match and the cost is linear. Quoted strings and one level of parentheses in nesting options keep working (#2336). The only difference: a lone " or ' inside unquoted parentheses within $t(...) is no longer matched. Affects 25.3.3 to 26.4.3. Thanks to Anisetti Chaitanya Eshwar Prasad for the responsible disclosure.
• fix(security): nest() now resolves $t(...) in a single pass and no longer nests text that came out of a resolved value. Every nested lookup reset the shared nesting regexp, so the loop started over from the beginning of the string after each match. That had two effects. First, a $t(...) inside a variable that the nested lookup deliberately kept literal (default skipOnVariables: true) was resolved anyway by the outer loop: with outer: 'A $t(inner) B' and inner: 'Hi {{name}}', t('outer', { name: '$t(secret)' }) rendered the secret translation. It now stays A Hi $t(secret) B, the same as without the outer nesting; with skipOnVariables: false it is still resolved. Second, the cost was quadratic when an unclosed $t( preceded many nestings, which matters when an app passes untrusted input as the key itself (t(userInput)): 20,000 nestings took ~1.4 s, now ~25 ms. The resolved value is now sliced into the result instead of going through String.replace, so $&, $`, $' and $$ stay literal as before (26.4.2).

v26.4.3

• perf: ResourceStore.hasLanguageSomeTranslations() no longer enumerates every key of a large bundle on each call. It ran Object.keys() on the whole bundle just to learn whether it had at least one key, and init() / changeLanguage() reach it three times per instance (once while picking the language, twice via setResolvedLanguage()). With large flat bundles and one i18next instance per SSR request reusing the same resources, that showed up as measurable CPU work before any t() call. Bundle objects already found non-empty are now remembered in a WeakSet shared across instances, so later checks are O(1): 2,000 inits with a 6,800-key bundle went from ~750 ms to ~20 ms, the same as a one-key bundle. Only the non-empty result is cached. No API removes single keys from a bundle, so a non-empty bundle stays non-empty, and empty bundles are re-checked every time, so keys added later (backend loads, addResource, addResourceBundle, direct or silent changes) count right away. The only edge case: a bundle emptied by hand with delete on every key while it is still in the store keeps counting as having translations; use removeResourceBundle() for that. Thanks @​dmchoi77 for the detailed report (#2449).

Changelog

Sourced from i18next's changelog.

26.4.4

• fix(security): the nesting regexp no longer backtracks exponentially (ReDoS) on an unclosed $t(. Its repeated group had overlapping alternatives ([^()"']+ inside (?:...)*?, and inside parentheses [^()] also matched quotes), so a string containing $t( without a closing ) made the engine try every way to split the text: about 2x the runtime per extra character, and a ~25 character value hung t() for minutes. With the default config this was reachable through any interpolated value (t('greet', { name: '$t(aaaaaaaaaaaaaaaaaaaaaaaa' })): escaping does not touch $, t or (, and the skipOnVariables check runs the regexp on the interpolated result, so nest: false did not help either. Every alternative now starts with a different character (plain char, ", ' or (), so there is only one way to match and the cost is linear. Quoted strings and one level of parentheses in nesting options keep working (#2336). The only difference: a lone " or ' inside unquoted parentheses within $t(...) is no longer matched. Affects 25.3.3 to 26.4.3. See advisory GHSA-5jr9-983r-c8x4, CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Thanks to Anisetti Chaitanya Eshwar Prasad for the responsible disclosure.
• fix(security): nest() now resolves $t(...) in a single pass and no longer nests text that came out of a resolved value. Every nested lookup reset the shared nesting regexp, so the loop started over from the beginning of the string after each match. That had two effects. First, a $t(...) inside a variable that the nested lookup deliberately kept literal (default skipOnVariables: true) was resolved anyway by the outer loop: with outer: 'A $t(inner) B' and inner: 'Hi {{name}}', t('outer', { name: '$t(secret)' }) rendered the secret translation. It now stays A Hi $t(secret) B, the same as without the outer nesting; with skipOnVariables: false it is still resolved. Second, the cost was quadratic when an unclosed $t( preceded many nestings, which matters when an app passes untrusted input as the key itself (t(userInput)): 20,000 nestings took ~1.4 s, now ~25 ms. The resolved value is now sliced into the result instead of going through String.replace, so $&, $`, $' and $$ stay literal as before (26.4.2).

26.4.3

• perf: ResourceStore.hasLanguageSomeTranslations() no longer enumerates every key of a large bundle on each call. It ran Object.keys() on the whole bundle just to learn whether it had at least one key, and init() / changeLanguage() reach it three times per instance (once while picking the language, twice via setResolvedLanguage()). With large flat bundles and one i18next instance per SSR request reusing the same resources, that showed up as measurable CPU work before any t() call. Bundle objects already found non-empty are now remembered in a WeakSet shared across instances, so later checks are O(1): 2,000 inits with a 6,800-key bundle went from ~750 ms to ~20 ms, the same as a one-key bundle. Only the non-empty result is cached. No API removes single keys from a bundle, so a non-empty bundle stays non-empty, and empty bundles are re-checked every time, so keys added later (backend loads, addResource, addResourceBundle, direct or silent changes) count right away. The only edge case: a bundle emptied by hand with delete on every key while it is still in the store keeps counting as having translations; use removeResourceBundle() for that. Thanks @​dmchoi77 for the detailed report (#2449).

Commits

• f6a7746 26.4.4
• 25988d5 build
• c9f8eba fix(security): nesting regexp ReDoS on unclosed $t( and single-pass nest(), c...
• 0d2845a 26.4.3
• a2dbe15 build
• e75843f perf: cache non-empty bundles in hasLanguageSomeTranslations, changelog v26.4.3
• edaea71 Fix TypeScript examples build and update them to i18next v26 (#2448)
• 4ebd19d docs: "For AI assistants" paragraph in the README and a fuller saveMissing JSDoc
• See full diff in compare view

Updates lint-staged from 17.5.1 to 17.6.0

Release notes

Sourced from lint-staged's releases.

v17.6.0

Minor Changes

• #1850 938d3f4 - Task functions like { title, task } can now use a logger function log() to emit output while the task runs. By default, the output will only be visible if the task fails, unless the --verbose option was used. Additionally, when the task rejects, the error will be shown in the output.

  import { defineConfig } from 'lint-staged/config'
  export default defineConfig({
  '*': {
  title: 'Fail if PDF files are committed',
  task: async (filepaths, { log }) => {
  const pdfFiles = filepaths.filter((f) => f.toLowerCase().endsWith('.pdf'))
  if (pdfFiles.length > 0) {
  log('PDF files should not be committed: %s', pdfFiles)
  throw new Error('Failed')
  }
  },
  },
  })

• #1854 30562bc - lint-staged now stages changes to all tracked files modified by tasks, including files that weren’t originally staged or didn’t match the configured globs. This can happen when your task has side-effects, or it's a function that ignores the staged files like () => "prettier --write .".

  If you have unstaged changes in a file and the task also edits that file, your unstaged changes will be staged too. Use --hide-unstaged to hide your changes while tasks run.

Patch Changes

• #1860 4296532 - The assignment of staged files to lint-staged configuration files (when using multiple, for example in a monorepo) has been rewritten to be more efficient. As a reminder, each staged file is assigned to exactly one configuration (the closest one), even if that config doesn't match the file in its globs.

• #1861 c45f28a - Fix running parallel tasks for a single glob, when tasks are created by a function. Nesting one level of arrays inside an array of tasks will result in the inner tasks running in parallel. This behavior should now be consistent when creating tasks using functions. In the following example eslint and prettier will run in parallel (for all files, when any JS files are staged):

  import { defineConfig } from 'lint-staged/config'
  export default defineConfig({
  '*.js': () => [['eslint --max-warnings=0 .', 'prettier --list-different .']],
  })

• #1859 f0ea69d - Various performance improvements from skipping redundant internal Git calls.

• #1856 69d7d17 - Partially staged changes are hidden in a uniquely-named patch file to avoid multiple invocations of lint-staged overwriting it. This makes it safer to run lint-staged in multiple worktrees at the same time.

Changelog

Sourced from lint-staged's changelog.

17.6.0

Minor Changes

• #1850 938d3f4 - Task functions like { title, task } can now use a logger function log() to emit output while the task runs. By default, the output will only be visible if the task fails, unless the --verbose option was used. Additionally, when the task rejects, the error will be shown in the output.

  import { defineConfig } from 'lint-staged/config'
  export default defineConfig({
  '*': {
  title: 'Fail if PDF files are committed',
  task: async (filepaths, { log }) => {
  const pdfFiles = filepaths.filter((f) => f.toLowerCase().endsWith('.pdf'))
  if (pdfFiles.length > 0) {
  log('PDF files should not be committed: %s', pdfFiles)
  throw new Error('Failed')
  }
  },
  },
  })

• #1854 30562bc - lint-staged now stages changes to all tracked files modified by tasks, including files that weren’t originally staged or didn’t match the configured globs. This can happen when your task has side-effects, or it's a function that ignores the staged files like () => "prettier --write .".

  If you have unstaged changes in a file and the task also edits that file, your unstaged changes will be staged too. Use --hide-unstaged to hide your changes while tasks run.

Patch Changes

• #1860 4296532 - The assignment of staged files to lint-staged configuration files (when using multiple, for example in a monorepo) has been rewritten to be more efficient. As a reminder, each staged file is assigned to exactly one configuration (the closest one), even if that config doesn't match the file in its globs.

• #1861 c45f28a - Fix running parallel tasks for a single glob, when tasks are created by a function. Nesting one level of arrays inside an array of tasks will result in the inner tasks running in parallel. This behavior should now be consistent when creating tasks using functions. In the following example eslint and prettier will run in parallel (for all files, when any JS files are staged):

  import { defineConfig } from 'lint-staged/config'
  export default defineConfig({
  '*.js': () => [['eslint --max-warnings=0 .', 'prettier --list-different .']],
  })

• #1859 f0ea69d - Various performance improvements from skipping redundant internal Git calls.

• #1856 69d7d17 - Partially staged changes are hidden in a uniquely-named patch file to avoid multiple invocations of lint-staged overwriting it. This makes it safer to run lint-staged in multiple worktrees at the same time.

Commits

• 48f9f4e Merge pull request #1857 from lint-staged/changeset-release/main
• 16b2e21 chore(changeset): release
• 195f156 docs: improve changeset
• 0ba6261 fix: create hidden directory only when required
• 66ac2de docs: fixes to changesets
• 80af8d7 Merge pull request #1863 from lint-staged/fix-issues
• e433488 fix: handle task editing a symlinked file to a regular file, and --fail-on-ch...
• e5019b3 fix: handle trailing newlines when detecting changed files
• 74efec8 ci: run Cygwin and MSYS2 tests on Node.js 26
• 655b7dc fix: use TypeScript types instead of JSDoc
• Additional commits viewable in compare view

Updates node-gyp from 13.0.2 to 13.1.0

Release notes

Sourced from node-gyp's releases.

v13.1.0

13.1.0 (2026-10-02)

Features

• update gyp-next to v0.22.3 (#3361) (729bfb8)

Bug Fixes

• accept --msvs_version as the README documents it (#3364) (8cca9c9)
• add Python 3.15 and update OS versions in tests.yml (#3369) (03c7b3b)
• let --loglevel on the command line override npm_config_loglevel (#3384) (2275aa9)

Core

• deps-dev: bump eslint to 10 and neostandard to 0.14.0-next.1 (#3374) (d389298)

Tests

• fix missing cb in fs.unlink (#3368) (e91cd76)
• fix non-ASCII addon cache path (#3370) (e6f699f)

Doc

• use Visual Studio 2026 in Windows setup instructions (#3367) (20bd442)

Miscellaneous

• deps: upgrade tar to 7.5.7 to address CVE-2026-24842 (#3375) (79048c9)
• use Visual Studio 2026 on windows-11-arm (#3380) (6feed93)

Changelog

Sourced from node-gyp's changelog.

13.1.0 (2026-10-02)

Features

• update gyp-next to v0.22.3 (#3361) (729bfb8)

Bug Fixes

• accept --msvs_version as the README documents it (#3364) (8cca9c9)
• add Python 3.15 and update OS versions in tests.yml (#3369) (03c7b3b)
• let --loglevel on the command line override npm_config_loglevel (#3384) (2275aa9)

Core

• deps-dev: bump eslint to 10 and neostandard to 0.14.0-next.1 (#3374) (d389298)

Tests

• fix missing cb in fs.unlink (#3368) (e91cd76)
• fix non-ASCII addon cache path (#3370) (e6f699f)

Doc

• use Visual Studio 2026 in Windows setup instructions (#3367) (20bd442)

Miscellaneous

• deps: upgrade tar to 7.5.7 to address CVE-2026-24842 (#3375) (79048c9)
• use Visual Studio 2026 on windows-11-arm (#3380) (6feed93)

Commits

• 399f6fa chore(main): release 13.1.0 (#3366)
• 2275aa9 fix: let --loglevel on the command line override npm_config_loglevel (#3384)
• 6feed93 ci: use Visual Studio 2026 on windows-11-arm (#3380)
• 729bfb8 feat: update gyp-next to v0.22.3 (#3361)
• 79048c9 chore(deps): upgrade tar to 7.5.7 to address CVE-2026-24842 (#3375)
• d389298 build(deps-dev): bump eslint to 10 and neostandard to 0.14.0-next.1 (#3374)
• 03c7b3b fix: add Python 3.15 and update OS versions in tests.yml (#3369)
• e6f699f test: fix non-ASCII addon cache path (#3370)
• e91cd76 test: fix missing cb in fs.unlink (#3368)
• 20bd442 docs: use Visual Studio 2026 in Windows setup instructions (#3367)
• Additional commits viewable in compare view

Updates prettier from 3.9.6 to 3.9.10

Release notes

Sourced from prettier's releases.

3.9.10

• Markdown: Update micromark-extension-gfm-table to fix the table parse issue on performance (#20266 by @​fisker)

🔗 Changelog

3.9.9

• Markdown: Fix text with $ been incorrectly parsed as math syntax (#20140 by @​fisker)

🔗 Changelog

3.9.8

• Markdown: Don't let Liquid objects interrupt paragraphs (#20087 by @​seiyab)

🔗 Changelog

3.9.7

• Support Angular 22.2
• Fix regressions in v3.9

🔗 Changelog

Changelog

Sourced from prettier's changelog.

3.9.10

diff

Markdown: Update micromark-extension-gfm-table to fix the table parse issue on performance (#20266 by @​fisker)

See micromark/micromark-extension-gfm-table@4f43ead for details.

3.9.9

diff

Markdown: Fix text with $ been incorrectly parsed as math syntax (#20140 by @​fisker)

<!-- Input -->
**Uses $FOO** from `a.sh` and `b.sh`, plus `$BAR` from `c.sh`, before anything else runs here.
<!-- Prettier 3.9.8 -->
Uses $FOO from a.sh and b.sh, plus $BARfromc.sh, before anything else runs here.
<!-- Prettier 3.9.9 -->
Uses $FOO from a.sh and b.sh, plus $BAR from c.sh, before anything else runs here.

3.9.8

diff

Markdown: Don't let Liquid objects interrupt paragraphs (#20087 by @​seiyab)

<!-- Input -->
If `module` is not a [`WebAssembly.Module`](https://github.com/prettier/prettier/blob/main/en-US/docs/WebAssembly/Reference/JavaScript_interface/Module) object instance, a
{{jsxref("TypeError")}} is thrown.
<!-- Prettier 3.9.7 -->
If module is not a WebAssembly.Module object instance, a
{{jsxref("TypeError")}} is thrown.
<!-- Prettier 3.9.8 -->
If module is not a WebAssembly.Module object instance, a
{{jsxref("TypeError")}} is thrown.

3.9.7

... (truncated)

Commits

• 1172b82 Release 3.9.10
• d014227 Update micromark-extension-gfm-table to fix the table parse issue on perfor...
• 953b908 Bump Prettier dependency to 3.9.9
• ad8a6bf Clean changelog_unreleased
• cdd17f2 Release 3.9.9
• dc7b896 Disable singleDollarTextMath in mdast-util-math (#20140)
• f9be58f Git blame ignore 3.9.8
• 88470cb Bump Prettier dependency to 3.9.8
• 9559cab Clean changelog_unreleased
• 4fc8ee8 Update dependents count
• Additional commits viewable in compare view

Updates storybook from 10.6.0 to 10.6.2

Release notes

Sourced from storybook's releases.

v10.6.2

10.6.2

• Angular-Vite: Require @​analogjs/vite-plugin-angular 2.7.3 or later - #36525, thanks @​valentinpalkovic!
• CLI: Fix hidden output of CLI commands on Yarn 1 - #36419, thanks @​kasperpeulen!
• Preact: Support Preact 11 - #36526, thanks @​ghengeveld!
• Security: Patch GHSA-f2ph-cmg5-wxc8 and GHSA-px85-f4q5-jh77 - #36726, thanks @​Sidnioulz!
• Typescript: Explicitly type enhanceArgTypes - #35664, thanks @​mrginglymus!

v10.6.1

10.6.1

• Addon A11y: Fix vision simulator color filters in Firefox - #36153, thanks @​ghengeveld!
• Addon Vitest: Support Vitest 5 browser tests - #36270, thanks @​valentinpalkovic!
• CLI: Fix vitest ERESOLVE on fresh Next.js apps. - #36310, thanks @​obvious-autobuild!
• Core: Fix build crash when ref reachability check fails mid-request - #36181, thanks @​shilman!
• Core: Restore the change-detection CTA in the sidebar - #36214, thanks @​ghengeveld!
• TanStack: Support both interpolatePath signatures - #36333, thanks @​BaconMan1168!
• Telemetry: One tools-command record per invocation with CLI toolset and tool names - #36210, thanks @​kasperpeulen!

Changelog

Sourced from storybook's changelog.

10.6.2

• Angular-Vite: Require @​analogjs/vite-plugin-angular 2.7.3 or later - #36525, thanks @​valentinpalkovic!
• CLI: Fix hidden output of CLI commands on Yarn 1 - #36419, thanks @​kasperpeulen!
• Preact: Support Preact 11 - #36526, thanks @​ghengeveld!
• Security: Patch GHSA-f2ph-cmg5-wxc8 and GHSA-px85-f4q5-jh77 - #36726, thanks @​Sidnioulz!
• Typescript: Explicitly type enhanceArgTypes - #35664, thanks @​mrginglymus!

10.6.1

• Addon A11y: Fix vision simulator color filters in Firefox - #36153, thanks @​ghengeveld!
• Addon Vitest: Support Vitest 5 browser tests - #36270, thanks @​valentinpalkovic!
• CLI: Fix vitest ERESOLVE on fresh Next.js apps. - #36310, thanks @​obvious-autobuild!
• Core: Fix build crash when ref reachability check fails mid-request - #36181, thanks @​shilman!
• Core: Restore the change-detection CTA in the sidebar - #36214, thanks @​ghengeveld!
• TanStack: Support both interpolatePath signatures - #36333, thanks @​BaconMan1168!
• Telemetry: One tools-command record per invocation with CLI toolset and tool names - #36210, thanks @​kasperpeulen!

Commits

• 5f00d7d Bump version from "10.6.1" to "10.6.2" [skip ci]
• b3ac816 Core: Cover component file name escaping in generated story imports
• 243c06b Merge pull request #36726 from storybookjs/sidnioulz/patch-internal-v11
• d0c7fa2 Merge pull request #36526 from storybookjs/validate/preact-11
• b49ded6 Merge pull request #36525 from storybookjs/fix/angular-vite-analog-2-7-3
• e067572 Merge pull request #35664 from storybookjs/bill/fix-leaky-types
• 01331a5 Merge pull request #36419 from storybookjs/kasper/sb-2060-yarn1-proxy-remote-...
• a17b725 Bump version from "10.6.0" to "10.6.1" [skip ci]
• 3077af4 Merge pull request #36310 from storybookjs/fix/init-vitest-range-stderr
• 22bf9df Merge pull request #36214 from storybookjs/ghengeveld/restore-change-detectio...
• Additional commits viewable in compare view

Updates turbo from 2.10.12 to 2.11.8

Release notes

Sourced from turbo's releases.

Turbore...

Description has been truncated

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.