Sourced from @​biomejs/biome's releases.

Biome CLI v2.0.0

Major Changes

• Biome now resolves globs and paths from the configuration. Before, paths and globs were resolved from the working directory.

• Biome now raises a warning diagnostic for suppression comments that have <explanation> as reason.

  <explanation> is provided as a placeholder when applying the suppression code fix from LSP editors.

• Removed the --config-path argument from the biome lsp-proxy and biome start commands.

  The option was overriding the configuration path for all workspaces opened in the Biome daemon, which led to a configuration mismatch problem when multiple projects are opened in some editors or IDEs.

  If you are using one of our official plugins for IDEs or editors, it is recommended to update it to the latest version of the plugin, or you will get unexpected behavior.

  If you are a developer of a plugin, please update your plugin to use the workspace/configuration response instead of using the --config-path argument. Biome's LSP will resolve a configuration in the workspace automatically, so it is recommended to keep it empty unless you are using a custom configuration path.

• Downgraded some code fixes to unsafe which were previously safe.

  The following rules have now a unsafe fix:

  • noFlatMapIdentity
  • noUnusedImports

  If you want to keep applying these fixes automatically, configure the rule fix as safe:

  {
    "linter": {
      "rules": {
        "correctness": {
          "noFlatMapIdentity": {
            "level": "error",
            "fix": "safe"
          },
          "noUnusedImports": {
            "level": "error",
            "fix": "safe"
          }
        }
      }
    }
  }

• Previously the lint rules noControlCharactersInRegex and noMisleadingCharacterClass checked both regular expression literals like /regex/ and dynamically built regular expressions like new RegExp("regex").

  Checking dynamically built regular expressions has many limitations, edge cases, and complexities.

... (truncated)

Sourced from @​biomejs/biome's changelog.

2.0.0

Major Changes

• Biome now resolves globs and paths from the configuration. Before, paths and globs were resolved from the working directory.

• Biome now raises a warning diagnostic for suppression comments that have <explanation> as reason.

  <explanation> is provided as a placeholder when applying the suppression code fix from LSP editors.

• Removed the --config-path argument from the biome lsp-proxy and biome start commands.

  The option was overriding the configuration path for all workspaces opened in the Biome daemon, which led to a configuration mismatch problem when multiple projects are opened in some editors or IDEs.

  If you are using one of our official plugins for IDEs or editors, it is recommended to update it to the latest version of the plugin, or you will get unexpected behavior.

  If you are a developer of a plugin, please update your plugin to use the workspace/configuration response instead of using the --config-path argument. Biome's LSP will resolve a configuration in the workspace automatically, so it is recommended to keep it empty unless you are using a custom configuration path.

• Downgraded some code fixes to unsafe which were previously safe.

  The following rules have now a unsafe fix:

  • noFlatMapIdentity
  • noUnusedImports

  If you want to keep applying these fixes automatically, configure the rule fix as safe:

  {
    "linter": {
      "rules": {
        "correctness": {
          "noFlatMapIdentity": {
            "level": "error",
            "fix": "safe"
          },
          "noUnusedImports": {
            "level": "error",
            "fix": "safe"
          }
        }
      }
    }
  }

• Previously the lint rules noControlCharactersInRegex and noMisleadingCharacterClass checked both regular expression literals like /regex/ and dynamically built regular expressions like new RegExp("regex").

  Checking dynamically built regular expressions has many limitations, edge cases, and complexities. In addition, other rules that lint regular expressions don't check dynamically built regular expressions.

... (truncated)

• be9076b chore: cleanup CHANGELOG
• 2b81d3f chore: fool release workflow step 2: reapply versions
• a259962 chore: fool release workflow step 1: revert versions
• 701c118 Fool release workflow step 2: reapply versions
• 323a580 Fool release workflow step 1: revert versions
• 242f739 Fool release workflow step 2: reapply versions
• d3175b0 Fool release workflow step 1: revert versions
• a711a3a Fool release workflow step 2: reapply versions
• c0b6316 Fool release workflow step 1: revert versions
• a56204c ci: release (#6351)
• Additional commits viewable in compare view

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)