chore(deps)(deps-dev): bump @biomejs/biome from 1.9.4 to 2.1.1

[dependabot]

Bumps @biomejs/biome from 1.9.4 to 2.1.1.

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.1.1

2.1.1

Patch Changes

• #6781 9bbd34f Thanks @​siketyan! - Fixed the FileFeaturesResult interface in the WASM API was defined as a mapped object but the actual value was a Map object.

• #6761 cf3c2ce Thanks @​dyc3! - Fixed #6759, a false positive for noFocusedTests that was triggered by calling any function with the name fit on any object.

  The following code will now pass the noFocusedTests rule:

  import foo from "foo";
  foo.fit();

What's Changed

• ci: correct restore path of the artifact by @​siketyan in biomejs/biome#6780
• fix(wasm): serialize map as a plain object by @​siketyan in biomejs/biome#6781
• ci: release by @​github-actions in biomejs/biome#6779
• docs: update contribution guide and pull request template by @​ematipico in biomejs/biome#6664

Full Changelog: https://github.com/biomejs/biome/compare/@​biomejs/js-api@​2.0.1...@​biomejs/biome@​2.1.1

Biome CLI v2.1.0

2.1.0

Minor Changes

• #6512 0c0bf82 Thanks @​arendjr! - The rule noFloatingPromises can now detect floating arrays of Promises.

  Invalid examples

  // This gets flagged because the Promises are not handled.
  [1, 2, 3].map(async (x) => x + 1);

  Valid examples

  await Promise.all([1, 2, 3].map(async (x) => x + 1));

• #6637 6918085 Thanks @​arendjr! - Type inference is now able to handle the sequence operator (,), as well as post- and pre-update operators: ++.

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.1.1

Patch Changes

• #6781 9bbd34f Thanks @​siketyan! - Fixed the FileFeaturesResult interface in the WASM API was defined as a mapped object but the actual value was a Map object.

• #6761 cf3c2ce Thanks @​dyc3! - Fixed #6759, a false positive for noFocusedTests that was triggered by calling any function with the name fit on any object.

  The following code will now pass the noFocusedTests rule:

  import foo from "foo";
  foo.fit();

2.1.0

Minor Changes

• #6512 0c0bf82 Thanks @​arendjr! - The rule noFloatingPromises can now detect floating arrays of Promises.

  Invalid examples

  // This gets flagged because the Promises are not handled.
  [1, 2, 3].map(async (x) => x + 1);

  Valid examples

  await Promise.all([1, 2, 3].map(async (x) => x + 1));

• #6637 6918085 Thanks @​arendjr! - Type inference is now able to handle the sequence operator (,), as well as post- and pre-update operators: ++.

  Example

  let x = 5;
  // We now infer that x++ resolves to a number, while the expression as a whole
  // becomes a Promise:
  x++, new Promise((resolve) => resolve("comma"));

• #6752 c9eaca4 Thanks @​arendjr! - Fixed #6646: .gitignore files are now picked up even when running Biome from a nested directory, or when the ignore file itself is ignored through files.includes.

• #6746 90aeead Thanks @​arendjr! - biome migrate no longer enables style rules that were recommended in v1, because that would be undesirable for users upgrading from 2.0.

... (truncated)

Commits

• eb62b71 ci: release (#6779)
• dcce75a ci: release (#6582)
• 1bfb5bb docs: fix typos in CHANGELOG & CONTRIBUTING (#6721)
• cd4a9bb feat(biome_js_analyse): added new option to rule to ignore unused function pa...
• 43d871e fix(formatter): trailing commas in json files (#6683)
• aee9ec7 fix(biome-js-analyze): move no_secrets options inside biome-rules-opt… (#6672)
• 74d27b9 refactor: share lint rule options (#5543)
• 1804abf Merge branch 'main' into next
• 153eda7 feat(biome_js_analyse): added new rule noMagicNumbers (#6562)
• 392b861 Merge branch 'main' into next
• 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)

Summary by Sourcery

Upgrade Biome CLI to v2.1.1 to introduce new linting capabilities, enhance type inference, fix key API and rule bugs, and refine upgrade behavior.

New Features:

• Enable detection of floating arrays of Promises in the noFloatingPromises rule
• Support type inference for the sequence operator and pre-/post-update (++) operators

Bug Fixes:

• Correct serialization of FileFeaturesResult in the WASM API
• Eliminate false positives in noFocusedTests when calling methods named fit

Enhancements:

• Improve .gitignore file resolution when running from nested directories
• Prevent biome migrate from re-enabling v1 style rules on upgrade

Chores:

• Bump @biomejs/biome from 1.9.4 to 2.1.1

[sourcery-ai]

Reviewer's Guide

This PR bumps the @biomejs/biome dev dependency from 1.9.4 to 2.1.1 by updating the version in package.json to pull in recent patch and minor fixes in the Biome CLI.

File-Level Changes

Change	Details	Files
Upgrade @biomejs/biome dev dependency	Updated the version specifier for @biomejs/biome in devDependencies Ran package install to apply the new version	package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.