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.4

Patch Changes

• #7415 d042f18 Thanks @qraqras! - Fixed #7212, now the useOptionalChain rule recognizes optional chaining using typeof (e.g., typeof foo !== 'undefined' && foo.bar).

• #7419 576baf4 Thanks @Conaclos! - Fixed #7323. noUnusedPrivateClassMembers no longer reports as unused TypeScript private members if the rule encounters a computed access on this.

  In the following example, member as previously reported as unused.
  It is no longer reported.

  class TsBioo {
    private member: number;
  
    set_with_name(name: string, value: number) {
      this[name] = value;
    }
  }

• #7248 75b6a0d Thanks @ematipico! - Added the new nursery lint rule noJsxLiterals, which disallows the use of string literals inside JSX.

  The rule catches these cases:

  <>
    <div>test</div> {/* test is invalid */}
    <>test</>
    <div>
      {/* this string is invalid */}
      asdjfl test foo
    </div>
  </>

• #7406 b906112 Thanks @mdevils! - Fixed an issue (💅 lint/correctness/useHookAtTopLevel: Reporting too many hooks #6393) where the useHookAtTopLevel rule reported excessive diagnostics for nested hook calls.

  The rule now reports only the offending top-level call site, not sub-hooks of composite hooks.

  // Before: reported twice (useFoo and useBar).
  function useFoo() {
    return useBar();
  }
  function Component() {
    if (cond) useFoo();
  }
  // After: reported once at the call to useFoo().

• #7418 00e1a6b Thanks @ematipico! - Fixed #7411. The Biome Language Server had a regression where opening an editor with a file already open wouldn't load the project settings correctly.

• #7142 53ff5ae Thanks @Netail! - Added the new nursery rule noDuplicateDependencies, which verifies that no dependencies are duplicated between the bundledDependencies, bundleDependencies, dependencies, devDependencies, overrides, optionalDependencies, and peerDependencies sections.

  For example, the following snippets will trigger the rule:

  {
    "dependencies": {
      "foo": ""
    },
    "devDependencies": {
      "foo": ""
    }
  }

  {
    "dependencies": {
      "foo": ""
    },
    "optionalDependencies": {
      "foo": ""
    }
  }

  {
    "dependencies": {
      "foo": ""
    },
    "peerDependencies": {
      "foo": ""
    }
  }

• #7441 733828c Thanks @ematipico! - Fixed #3824. Now the option CLI --color is correctly applied to logging too.

@biomejs/backend-jsonrpc@2.0.16

@biomejs/cli-darwin-arm64@2.2.4

@biomejs/cli-darwin-x64@2.2.4

@biomejs/cli-linux-arm64@2.2.4

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

@biomejs/cli-linux-x64@2.2.4

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

@biomejs/cli-win32-arm64@2.2.4

@biomejs/cli-win32-x64@2.2.4

@biomejs/wasm-bundler@2.2.4

@biomejs/wasm-nodejs@2.2.4

@biomejs/wasm-web@2.2.4

[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.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}