[dependabot]

Bumps @biomejs/biome from 2.5.15 to 2.6.6.

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.6.6

2.6.6

Patch Changes

• #12887 da0422e Thanks @​dyc3! - Added the new nursery rule noArrayMethodsOnArguments. It reports calls to array methods on the arguments object, which isn't an array, so these calls throw a TypeError when the code runs.

  function sum() {
    return arguments.reduce((total, value) => total + value, 0);
  }

• #12877 cd9e10f Thanks @​dyc3! - Added the nursery rule noConstantComparisons, which reports && and || conditions that can never be true, are always true, or contain a check with no effect.

  if (statusCode <= 400 && statusCode > 500) {}

• #12876 a7c9586 Thanks @​dyc3! - Added the nursery rule noErasingOperation, which disallows operations with 0 that always result in zero: multiplying by 0, a bitwise AND with 0, and dividing 0 by a number. The other value in these operations has no effect on the result, which usually means the code has a mistake.

  const total = price * 0;

• #12841 e954f55 Thanks @​dyc3! - Added the nursery rule noNegatedArrayPredicate, which reports negated calls to Array#some() and Array#every() and suggests moving the negation into the callback function.

  // Invalid: use `array.every((item) => !isUnicorn(item))` instead.
  const isMissing = !array.some((item) => isUnicorn(item));

• #12888 15039f7 Thanks @​dyc3! - Added the new nursery rule noNumberArgumentOutOfRange, which reports number literal arguments of toString(), toFixed(), toExponential() and toPrecision() that are outside the range the method accepts. These calls throw a RangeError at runtime.

  value.toString(64);

• #12889 1cd7520 Thanks @​dyc3! - Added the nursery rule noSharedBranchCode, which reports code that is repeated at the start or end of every branch of an if statement. That code runs no matter which branch is taken, so it can be moved before or after the if statement.

  if (condition) {
    doSomething();
    cleanup();
  } else {
    doSomethingElse();
    cleanup();
  }

... (truncated)

Commits

• 09ee04d ci: release (#12938)
• 191111d feat(lint): add usePackageJsonEngines (#12310)
• 0538e30 feat(lint): add usePackageJsonCpu (#12309)
• 6b73fcf feat(lint): add noUninvokedArrayCallback (#12890)
• 1cd7520 feat(lint): add noSharedBranchCode (#12889)
• 15039f7 feat(lint): add noNumberArgumentOutOfRange (#12888)
• da0422e feat(lint): add noArrayMethodsOnArguments (#12887)
• 3bb18d8 feat(lint): add useNextScriptForGoogleAnalytics (#12886)
• cd9e10f feat(lint): add noConstantComparisons (#12877)
• a7c9586 feat(lint): add noErasingOperation (#12876)
• 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 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)

[coderabbitai]

Important

Review skipped

Bot user detected.

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

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: df31a8bf-7178-49c2-9f4b-e26bc9d02ae5

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

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-10T12:45:21.563463Z	8508f78	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8508f786a3

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Format Markdown before upgrading to Biome 2.6

When the lint job runs npm run lint, this upgrade makes Biome recognize and format the Markdown files already selected by biome.json. Biome 2.6 introduced Markdown support, its Markdown formatter is enabled by default, and biome check checks formatting (Biome 2.6 announcement, CLI reference, configuration reference). README.md has not been formatted accordingly—for example, its parser-options table has unaligned delimiters at line 114—so lint:biome will report formatter differences and fail the repository's lint CI job. Format the selected Markdown files in this commit or explicitly exclude/disable Markdown formatting.

Useful? React with 👍 / 👎.