Bump @biomejs/biome from 1.9.4 to 2.4.12 in the dev-tooling group

[dependabot]

Bumps the dev-tooling group with 1 update: @biomejs/biome.

Updates @biomejs/biome from 1.9.4 to 2.4.12

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.4.12

2.4.12

Patch Changes

• #9376 9701a33 Thanks @​dyc3! - Added the nursery/noIdenticalTestTitle lint rule. This rule disallows using the same title for two describe blocks or two test cases at the same nesting level.

  describe("foo", () => {});
  describe("foo", () => {
    // invalid: same title as previous describe block
    test("baz", () => {});
    test("baz", () => {}); // invalid: same title as previous test case
  });

• #9889 7ae83f2 Thanks @​dyc3! - Improved the diagnostics for useForOf to better explain the problem, why it matters, and how to fix it.

• #9916 27dd7b1 Thanks @​Jayllyz! - Added a new nursery rule noComponentHookFactories, that disallows defining React components or custom hooks inside other functions.

  For example, the following snippets trigger the rule:

  function createComponent(label) {
    function MyComponent() {
      return <div>{label}</div>;
    }
    return MyComponent;
  }

  function Parent() {
    function Child() {
      return <div />;
    }
    return <Child />;
  }

• #9980 098f1ff Thanks @​ematipico! - Fixed #9941: Biome now emits a warning diagnostic when a file exceed the files.maxSize limit.

• #9942 9956f1d Thanks @​dyc3! - Fixed #9918: useConsistentTestIt no longer panics when applying fixes to chained calls such as test.for([])("x", () => {});.

• #9891 4d9ac51 Thanks @​dyc3! - Improved the noGlobalObjectCalls diagnostic to better explain why calling global objects like Math or JSON is invalid and how to fix it.

• #9902 3f4d103 Thanks @​ematipico! - Fixed #9901: the command lint --write is now idempotent when it's run against HTML-ish files that contains scripts and styles.

• #9891 4d9ac51 Thanks @​dyc3! - Improved the noMultiStr diagnostic to explain why escaped multiline strings are discouraged and what to use instead.

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.4.12

Patch Changes

• #9376 9701a33 Thanks @​dyc3! - Added the nursery/noIdenticalTestTitle lint rule. This rule disallows using the same title for two describe blocks or two test cases at the same nesting level.

  describe("foo", () => {});
  describe("foo", () => {
    // invalid: same title as previous describe block
    test("baz", () => {});
    test("baz", () => {}); // invalid: same title as previous test case
  });

• #9889 7ae83f2 Thanks @​dyc3! - Improved the diagnostics for useForOf to better explain the problem, why it matters, and how to fix it.

• #9916 27dd7b1 Thanks @​Jayllyz! - Added a new nursery rule noComponentHookFactories, that disallows defining React components or custom hooks inside other functions.

  For example, the following snippets trigger the rule:

  function createComponent(label) {
    function MyComponent() {
      return <div>{label}</div>;
    }
    return MyComponent;
  }

  function Parent() {
    function Child() {
      return <div />;
    }
    return <Child />;
  }

• #9980 098f1ff Thanks @​ematipico! - Fixed #9941: Biome now emits a warning diagnostic when a file exceed the files.maxSize limit.

• #9942 9956f1d Thanks @​dyc3! - Fixed #9918: useConsistentTestIt no longer panics when applying fixes to chained calls such as test.for([])("x", () => {});.

• #9891 4d9ac51 Thanks @​dyc3! - Improved the noGlobalObjectCalls diagnostic to better explain why calling global objects like Math or JSON is invalid and how to fix it.

• #9902 3f4d103 Thanks @​ematipico! - Fixed #9901: the command lint --write is now idempotent when it's run against HTML-ish files that contains scripts and styles.

• #9891 4d9ac51 Thanks @​dyc3! - Improved the noMultiStr diagnostic to explain why escaped multiline strings are discouraged and what to use instead.

• #9966 322675e Thanks @​siketyan! - Fixed #9113: Biome now parses and formats @media and other conditional blocks correctly inside embedded CSS snippets.

... (truncated)

Commits

• baaacfc ci: release (#9890)
• e0ba71d feat: implement useIframeSandbox (#9949)
• 2cff700 feat(lint/js): add useVarsOnTop (#9861)
• 27dd7b1 feat(react/js): add noComponentHookFactories (#9916)
• 0d0e611 feat(js_analyze): implement useReactAsyncServerFunction (#9909)
• f1c1363 feat(lint/js): add useStringStartsEndsWith (#9796)
• d417803 feat(js_analyze): implement noJsxNamespace (#9913)
• 9701a33 feat(lint/js): add noIdenticalTestTitle (#9376)
• c499f46 feat(lint): implement useReduceTypeParameter nursery rule (#9577)
• 40bd180 feat(lint/js): add noExcessiveSelectorClasses (#9866)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​biomejs/biome since your current version.

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

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[greptile-apps]

Greptile Summary

This PR bumps @biomejs/biome from 1.9.4 to 2.4.12 — a major version upgrade. The lockfile is correctly updated, but the companion biome.json was not migrated to the v2 configuration format, which introduces two concrete breakages:

• The $schema URL still points to the v1.9.4 schema, so IDE validation and config type-checking will silently use the wrong schema.
• The top-level organizeImports field was removed in Biome v2; it must be replaced with assist.actions.source.organizeImports. Without this change, import sorting will stop working after the upgrade.

Biome ships a first-party migration tool (biome migrate --write) that handles both of these automatically and should be run before this PR is merged.

Confidence Score: 3/5

Not safe to merge without updating biome.json — the organizeImports feature will silently break and the config schema will be wrong.

This is a major version bump (1.x → 2.x) with known breaking configuration changes. The biome.json was not updated alongside the package version: the top-level organizeImports field was removed in Biome v2 and import sorting will stop working silently, and the $schema URL remains on v1.9.4. Both issues are straightforwardly fixed by running biome migrate --write, but until that's done this PR is incomplete.

biome.json requires migration to Biome v2 format before this PR can be safely merged.

Important Files Changed

Filename	Overview
package.json	Bumps @biomejs/biome dev dependency from ^1.9.4 to ^2.4.12 — a major version change that requires a companion biome.json migration.
pnpm-lock.yaml	Lockfile updated consistently with all @biomejs/biome and @biomejs/cli-* platform packages bumped from 1.9.4 to 2.4.12.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[package.json\nbumped to @biomejs/biome ^2.4.12] --> B[pnpm-lock.yaml\nall cli platform packages updated]
    A --> C{biome.json\nmigrated?}
    C -- No --> D[schema URL still v1.9.4\nIDE validates against wrong schema]
    C -- No --> E[organizeImports at top-level\nremoved in v2 — import sorting broken]
    C -- Fix --> F[Run: biome migrate --write\nautomatically handles both changes]
    F --> G[schema updated to 2.4.12\nassist.actions.source.organizeImports added]

Loading

Comments Outside Diff (2)

1. biome.json, line 2 (link)

   Schema URL not updated for Biome v2

   The $schema still points to 1.9.4 while the installed version is 2.4.12. This means IDEs and validators will use the v1 schema to validate the config, which doesn't reflect the actual v2 schema — so breaking changes in the config structure will go silently undetected.

2. biome.json, line 3 (link)

   organizeImports removed as a top-level field in Biome v2

   Biome v2 removed the top-level organizeImports field. Import organization is now controlled via the assist section. With this config still in place, Biome v2 will likely ignore or warn about this unknown field, meaning import sorting may silently stop working.

   Per the Biome v2 upgrade guide, the migration is:

   // Before (v1)
   "organizeImports": { "enabled": true }
   
   // After (v2)
   "assist": { "actions": { "source": { "organizeImports": "on" } } }

   Running npx @biomejs/biome migrate --write will automatically apply this (and other) required config migrations.

_{Reviews (1): Last reviewed commit: "Bump @biomejs/biome from 1.9.4 to 2.4.12..." | Re-trigger Greptile}

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml