chore(deps-dev): bump @biomejs/biome from 1.6.4 to 2.2.5

[dependabot]

Bumps @biomejs/biome from 1.6.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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6b4ee0f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

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

Project	Deployment	Preview	Updated (UTC)
app.venus.io	Error		Oct 10, 2025 9:30pm
dapp-preview	Error		Oct 10, 2025 9:30pm
dapp-testnet	Error		Oct 10, 2025 9:30pm

1 Skipped Deployment

Project	Deployment	Preview	Updated (UTC)
venus.io	Skipped		Oct 10, 2025 9:30pm

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.