chore(deps): bump the patch-updates group across 1 directory with 6 updates

[dependabot]

Bumps the patch-updates group with 6 updates in the / directory:

Package	From	To
@iconify-json/material-symbols	1.2.39	1.2.40
katex	0.16.22	0.16.23
svelte	5.39.6	5.39.8
tailwindcss	3.4.17	3.4.18
typescript	5.9.2	5.9.3
@biomejs/biome	2.2.4	2.2.5

Updates @iconify-json/material-symbols from 1.2.39 to 1.2.40

Commits

• See full diff in compare view

Updates katex from 0.16.22 to 0.16.23

Release notes

Sourced from katex's releases.

v0.16.23

0.16.23 (2025-10-03)

Bug Fixes

• Support \def with arguments via macros option (#4087) (80a8158)

Changelog

Sourced from katex's changelog.

0.16.23 (2025-10-03)

Bug Fixes

• Support \def with arguments via macros option (#4087) (80a8158)

Commits

• eed3ea5 chore(release): 0.16.23 [ci skip]
• 80a8158 fix: Support \def with arguments via macros option (#4087)
• 049ed98 docs: Update Delimiters table to add / and correct \lt, \gt rendering (...
• 9fb6313 docs: correct closing tag and fix some spelling errors (#4063)
• See full diff in compare view

Updates svelte from 5.39.6 to 5.39.8

Release notes

Sourced from svelte's releases.

[email protected]

Patch Changes

• fix: check boundary pending attribute at runtime on server (#16855)

• fix: preserve tuple type in $state.snapshot (#16864)

• fix: allow await in svelte:boundary without pending (#16857)

• fix: update bind:checked error message to clarify usage with radio inputs (#16874)

[email protected]

Patch Changes

• chore: simplify batch logic (#16847)

• fix: rebase pending batches when other batches are committed (#16866)

• fix: wrap async children in $$renderer.async (#16862)

• fix: silence label warning for buttons and anchor tags with title attributes (#16872)

• fix: coerce nullish <title> to empty string (#16863)

Changelog

Sourced from svelte's changelog.

5.39.8

Patch Changes

• fix: check boundary pending attribute at runtime on server (#16855)

• fix: preserve tuple type in $state.snapshot (#16864)

• fix: allow await in svelte:boundary without pending (#16857)

• fix: update bind:checked error message to clarify usage with radio inputs (#16874)

5.39.7

Patch Changes

• chore: simplify batch logic (#16847)

• fix: rebase pending batches when other batches are committed (#16866)

• fix: wrap async children in $$renderer.async (#16862)

• fix: silence label warning for buttons and anchor tags with title attributes (#16872)

• fix: coerce nullish <title> to empty string (#16863)

Commits

• 5c847ff Version Packages (#16877)
• 949c026 fix: preserve tuple type in $state.snapshot (#16864)
• 4999734 fix: check boundary pending attribute at runtime on server (#16855)
• 4f653dd fix: update error message to clarify usage with radio inputs (#16874)
• 31541c8 fix: allow await in svelte boundary without pending (#16857)
• e9cd45a Version Packages (#16848)
• 46c10d0 fix: missing title warning for buttons and anchor tags (#16872)
• 25cbdc8 fix: merge batches (#16866)
• 87f7e97 fix: wrap async children in $$renderer.async (#16862)
• 8895bd4 fix: coerce nullish \<title> to empty string (#16863)
• Additional commits viewable in compare view

Updates tailwindcss from 3.4.17 to 3.4.18

Release notes

Sourced from tailwindcss's releases.

v3.4.18

Fixed

• Improve support for raw supports-[…] queries in arbitrary values (#13605)
• Fix require.cache error when loaded through a TypeScript file in Node 22.18+ (#18665)
• Support import.meta.resolve(…) in configs for new enough Node.js versions (#18938)
• Allow using newer versions of postcss-load-config for better ESM and TypeScript PostCSS config support with the CLI (#18938)
• Remove irrelevant utility rules when matching important classes (#19030)

Changelog

Sourced from tailwindcss's changelog.

[3.4.18] - 2024-10-01

Fixed

• Improve support for raw supports-[…] queries in arbitrary values (#13605)
• Fix require.cache error when loaded through a TypeScript file in Node 22.18+ (#18665)
• Support import.meta.resolve(…) in configs for new enough Node.js versions (#18938)
• Allow using newer versions of postcss-load-config for better ESM and TypeScript PostCSS config support with the CLI (#18938)
• Remove irrelevant utility rules when matching important classes (#19030)

Commits

• See full diff in compare view

Updates typescript from 5.9.2 to 5.9.3

Release notes

Sourced from typescript's releases.

TypeScript 5.9.3

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement

• fixed issues query for Typescript 5.9.0 (Beta).
• fixed issues query for Typescript 5.9.1 (RC).
• No specific changes for TypeScript 5.9.2 (Stable)
• fixed issues query for Typescript 5.9.3 (Stable).

Downloads are available on:

• npm

Commits

• c63de15 Bump version to 5.9.3 and LKG
• 8428ca4 🤖 Pick PR #62438 (Fix incorrectly ignored dts file fr...) into release-5.9 (#...
• a131cac 🤖 Pick PR #62351 (Add missing Float16Array constructo...) into release-5.9 (#...
• 0424333 🤖 Pick PR #62423 (Revert PR 61928) into release-5.9 (#62425)
• bdb641a 🤖 Pick PR #62311 (Fix parenthesizer rules for manuall...) into release-5.9 (#...
• 0d9b9b9 🤖 Pick PR #61978 (Restructure CI to prepare for requi...) into release-5.9 (#...
• 2dce0c5 Intentionally regress one buggy declaration output to an older version (#62163)
• See full diff in compare view

Updates @biomejs/biome from 2.2.4 to 2.2.5

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.2.5

2.2.5

Patch Changes

• #7597 5c3d542 Thanks @​arendjr! - Fixed #6432: useImportExtensions now works correctly with aliased paths.

• #7269 f18dac1 Thanks @​CDGardner! - Fixed #6648, where Biome's noUselessFragments contained inconsistencies with ESLint for fragments only containing text.

  Previously, Biome would report that fragments with only text were unnecessary under the noUselessFragments rule. Further analysis of ESLint's behavior towards these cases revealed that text-only fragments (<>A</a>, <React.Fragment>B</React.Fragment>, <RenamedFragment>B</RenamedFragment>) would not have noUselessFragments emitted for them.

  On the Biome side, instances such as these would emit noUselessFragments, and applying the suggested fix would turn the text content into a proper JS string.

  // Ended up as: - const t = "Text"
  const t = <>Text</>
  // Ended up as: - const e = t ? "Option A" : "Option B"
  const e = t ? <>Option A</> : <>Option B</>
  /* Ended up as:
  function someFunc() {
  return "Content desired to be a multi-line block of text."
  }
  */
  function someFunc() {
  return <>
  Content desired to be a multi-line
  block of text.
  <>
  }

  The proposed update was to align Biome's reaction to this rule with ESLint's; the aforementioned examples will now be supported from Biome's perspective, thus valid use of fragments.

  // These instances are now valid and won't be called out by noUselessFragments.
  const t = <>Text</>
  const e = t ? <>Option A</> : <>Option B</>
  function someFunc() {
  return <>
  Content desired to be a multi-line
  block of text.
  <>
  }

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.2.5

Patch Changes

• #7597 5c3d542 Thanks @​arendjr! - Fixed #6432: useImportExtensions now works correctly with aliased paths.

• #7269 f18dac1 Thanks @​CDGardner! - Fixed #6648, where Biome's noUselessFragments contained inconsistencies with ESLint for fragments only containing text.

  Previously, Biome would report that fragments with only text were unnecessary under the noUselessFragments rule. Further analysis of ESLint's behavior towards these cases revealed that text-only fragments (<>A</a>, <React.Fragment>B</React.Fragment>, <RenamedFragment>B</RenamedFragment>) would not have noUselessFragments emitted for them.

  On the Biome side, instances such as these would emit noUselessFragments, and applying the suggested fix would turn the text content into a proper JS string.

  // Ended up as: - const t = "Text"
  const t = <>Text</>
  // Ended up as: - const e = t ? "Option A" : "Option B"
  const e = t ? <>Option A</> : <>Option B</>
  /* Ended up as:
  function someFunc() {
  return "Content desired to be a multi-line block of text."
  }
  */
  function someFunc() {
  return <>
  Content desired to be a multi-line
  block of text.
  <>
  }

  The proposed update was to align Biome's reaction to this rule with ESLint's; the aforementioned examples will now be supported from Biome's perspective, thus valid use of fragments.

  // These instances are now valid and won't be called out by noUselessFragments.
  const t = <>Text</>
  const e = t ? <>Option A</> : <>Option B</>
  function someFunc() {
  return <>
  Content desired to be a multi-line
  block of text.
  <>
  }

• #7498 002cded Thanks @​siketyan! - Fixed #6893: The useExhaustiveDependencies rule now correctly adds a dependency that is captured in a shorthand object member. For example:

... (truncated)

Commits

• 521d149 ci: release (#7478)
• cadad2c feat(lint): implement noVueDuplicateKeys rule (#7542)
• 9637f93 feat: add useConsistentArrowReturn options (#7457)
• 1b61631 feat(lint): add noReactForwardRef rule (#7509)
• 74d3c56 chore: add convex to bronze sponsors (#7566)
• 3f06e19 feat(linter): implement noDeprecatedImports (#7520)
• a0039fd feat(linter): implement noUnusedExpressions (#7511)
• fd126d7 chore: fix markdown syntax in changelog
• b2da976 chore: fix changelog formatting
• 0109940 chore: repair changelog (#7477)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
fuwari-yags	Ready	Preview	Comment	Oct 3, 2025 8:16pm