---
changelog:
  category: Release
  version: ultracite@7.6.1
date: '2026-04-22T16:10:53Z'
seo:
  description: >-
    Disable the typescript/prefer-readonly-parameter-types Oxlint rule. While
    the rule is useful for user-authored types, it fires on virtually every
    parameter…
title: ultracite@7.6.1
type: changelog
---
## Patch Changes

-   2fbded9: Disable the `typescript/prefer-readonly-parameter-types` Oxlint rule. While the rule is useful for user-authored types, it fires on virtually every parameter that touches a third-party type (Express `Request`/`Response`, React events, Node `Buffer`, ORM models, DOM APIs) because those types aren't deeply readonly internally — leaving users with unfixable violations. Matches the existing ESLint config, which already has this rule off.
-   617affd: Fix `dist/`, `.next/`, `**/*.gen.*`, and other strong-negation (`!!`) ignore globs being dropped when a consumer's `biome.jsonc` extends `ultracite/biome/core` and also defines its own `files.includes`. The globs moved into `config/shared/ignores.jsonc` in 7.5.9 were transitively extended through `biome/core`, and Biome's extend merge doesn't carry `files.includes` through a two-level chain when the middle config lacks its own entry. The patterns are now inlined directly in `biome/core`'s `files.includes` (still generated from `config/shared/ignores.mjs`), matching the pre-7.5.9 behavior.
-   d681e08: Remove the nonexistent `import-x/enforce-node-protocol-usage` rule from the ESLint core config, which caused ESLint 9 to throw `Could not find "enforce-node-protocol-usage" in plugin "import-x"`. Node protocol enforcement is already covered by `unicorn/prefer-node-protocol`.
