ci: release

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@biomejs/biome@2.2.1

Patch Changes

• #7266 b270bb5 Thanks @ematipico! - Fixed an issue where Biome got stuck when analyzing some files. This is usually caused by a bug in the inference engine. Now Biome has some guards in place in case the number of types grows too much, and if that happens, a diagnostic is emitted and the inference is halted.

• #7281 6436180 Thanks @ematipico! - Fixed an issue where the function scanProject wouldn't work as expected.

• #7285 1511d0c Thanks @rriski! - Partially fixed #6782: JSX node kinds are now supported in GritQL AST nodes.

• #7249 dff85c0 Thanks @ematipico! - Fixed #748, where Biome Language Server didn't show the unsafe fixes when requesting the quick fixes. Now all LSP editors will show also opt-in, unsafe fixes.

• #7266 b270bb5 Thanks @ematipico! - Fixed #7020: Resolved an issue with analysing types of static member expressions involving unions. If the object type was a union that referenced nested unions, it would trigger an infinite loop as it tried to keep expanding nested unions, and the set of types would grow indefinitely.

• #7209 679b70e Thanks @patrickshipe! - Resolved an overcorrection in useImportExtensions when importing explicit index files.

  Imports that explicitly reference an index file are now preserved and no longer rewritten to nested index paths.

  Example

  // Before
  -      import "./sub/index";
  +      import "./sub/index/index.js";
  
  // After
  -      import "./sub/index";
  +      import "./sub/index.js";

• #7270 953f9c6 Thanks @arendjr! - Fixed #6172: Resolved an issue with inferring types for rest parameters. This issue caused rest-parameter types to be incorrect, and in some cases caused extreme performance regressions in files that contained many methods with rest-parameter definitions.

• #7234 b7aa111 Thanks @JeetuSuthar! - Fixed #7233: The useIndexOf rule now correctly suggests using indexOf() instead of findIndex().

  The diagnostic message was incorrectly recommending Array#findIndex() over Array#indexOf(), when it should recommend the opposite for simple equality checks.

• #7283 0b07f45 Thanks @ematipico! - Fixed #7236. Now Biome correctly migrates JSONC configuration files when they are passed using --config-path.

• #7239 1d643d8 Thanks @minht11! - Fixed an issue where Svelte globals ($state and so on) were not properly recognized inside .svelte.test.ts/js and .svelte.spec.ts/js files.

• #7264 62fdbc8 Thanks @ematipico! - Fixed a regression where when using --log-kind-pretty wasn't working anymore as expected.

@biomejs/wasm-bundler@2.2.1

Patch Changes

• #7281 6436180 Thanks @ematipico! - Fixed an issue where the function scanProject wouldn't work as expected.

@biomejs/wasm-nodejs@2.2.1

Patch Changes

• #7281 6436180 Thanks @ematipico! - Fixed an issue where the function scanProject wouldn't work as expected.

@biomejs/wasm-web@2.2.1

Patch Changes

• #7281 6436180 Thanks @ematipico! - Fixed an issue where the function scanProject wouldn't work as expected.

@biomejs/backend-jsonrpc@2.0.13

@biomejs/cli-darwin-arm64@2.2.1

@biomejs/cli-darwin-x64@2.2.1

@biomejs/cli-linux-arm64@2.2.1

@biomejs/cli-linux-arm64-musl@2.2.1

@biomejs/cli-linux-x64@2.2.1

@biomejs/cli-linux-x64-musl@2.2.1

@biomejs/cli-win32-arm64@2.2.1

@biomejs/cli-win32-x64@2.2.1

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.