---
changelog:
  category: Release
  version: ultracite@8.3.0
date: '2026-11-18T05:10:03Z'
seo:
  description: >-
    Add an opt-in ultracite/oxlint/landmines preset for @interfere/landmines,
    Oxlint rules for the shortcuts a coding agent takes to get a green check.
    All ten…
title: ultracite@8.3.0
type: changelog
---
## Minor Changes

- 247352f: Add an opt-in `ultracite/oxlint/landmines` preset for [`@interfere/landmines`](https://github.com/interfere-inc/landmines), Oxlint rules for the shortcuts a coding agent takes to get a green check. All ten rules run at `error`: `no-test-doubles`, `strict-msw`, `no-fixed-sleep`, `no-unsignaled-poll` and `no-flake-masking` for tests, plus `no-comments`, `colocated-tests`, `test-file-names`, `package-exports` and `no-explicit-return-types`. Enable it with `ultracite init --linter oxlint --js-plugins @interfere/landmines`, or extend it alongside `ultracite/oxlint/core` after installing `@interfere/landmines`. `doctor` and `upgrade` check and reinstall the package for configs that load it.
  
  The preset is Oxlint-only. Its `no-comments` rule rejects the `SAFETY:` comment that `anti-slop/require-safety-comment-for-type-assertion` requires ([interfere-inc/landmines#4](https://github.com/interfere-inc/landmines/issues/4)), so turn one of the two off when extending both presets.

## Patch Changes

- f23eb8e: `ultracite fix --claude` and `fix --codex` now give the agent the rule description and documentation link for `jsdoc-js/*` and `tsdoc/*` diagnostics on Oxlint. Oxlint's report has neither for a rule that comes from a JS plugin, so Ultracite reads them from the plugin, but only did so for `eslint-plugin-github`, `eslint-plugin-sonarjs` and `oxlint-plugin-react-doctor`. The two documentation plugins were left with the one-line message alone.
- 39577c0: Running `ultracite init` again no longer rewrites an `.aider.conf.yml` that already has Ultracite's settings. The file was re-serialised even when nothing needed changing, which normalised its spacing (`read:   [AGENTS.md]` became `read: [ AGENTS.md ]`, and aligned comments moved) and listed it as updated. It is now left exactly as written unless a key changes.
- d0219d3: `ultracite fix --claude` and `fix --codex` on Biome now ask `biome explain` about each rule once. A rule Biome couldn't describe was not remembered, so `biome explain` ran again for every diagnostic of that rule, which slowed down a run with many of them.
- 9b94a7a: `ultracite doctor` now gives the right advice when a `.oxlintrc.jsonc` or `.oxfmtrc.jsonc` sits next to the TypeScript config. It told you to delete one of the two files, where for a `.json` file it says to run `ultracite init`, which migrates the JSON config into the TypeScript one. `init` migrates `.jsonc` files the same way, so `doctor` now says so. When three config files are present, the message also reads "are all present" instead of "are both present".
- 88f51b2: In a monorepo on the ESLint provider, `ultracite init` now gives a workspace config its framework's type-aware add-on when the root `eslint.config.*` imports `ultracite/eslint/type-aware` with single quotes. Only a double-quoted import was recognised, so after a formatter rewrote the root config with single quotes, a new workspace config was written without `ultracite/eslint/<framework>/type-aware`.
- 984ef22: `ultracite init` no longer reformats `package.json` when it updates a `lint-staged` config stored there. The file was written back with two-space indentation and LF line endings, so a tab-indented or CRLF `package.json` came back with every line changed. It now keeps the file's own indentation and line endings, as the other `package.json` edits `init` makes already do.
- b21013f: `ultracite init` no longer writes a duplicate key into `oxlint.config.ts` when the key it is checking for is quoted or has a comment on the line above. Two cases were affected. With `--type-aware`, a config whose own `options` sat under a comment got a second `options: { typeAware: true }` ahead of it, which the project's `options` then overrode, so type-aware linting stayed off without the usual notice. And when a leftover `.oxlintrc.json` was migrated, a key such as `"rules"` that the TypeScript config already set was added again from the JSON file, where it took precedence. Both now compare the parsed key, so the config's own value is kept.
- 3c0aef1: On Oxlint, `ultracite check` and `ultracite fix` no longer fail when given a file Oxlint doesn't lint whose path contains glob characters, such as `app/[slug]/styles.css` or `app/[slug]/data.json`. The path was taken for a glob and passed to Oxlint, which exited 1 with "No files found to lint". That broke lint-staged and editor hooks whenever the only changed file was a stylesheet, JSON or Markdown file inside a Next.js dynamic route folder. A path that exists on disk is now treated as a file, and Oxlint is skipped for it as it is for any other file it doesn't lint.
- ab7aca8: `ultracite init`, `doctor` and `upgrade` now read an Oxlint JS plugin selection written with single quotes, such as `selectJsPlugins(['sonarjs', 'github'])`. Only double-quoted names were recognised, so in a project whose formatter uses single quotes the selection read as empty: running `init` again removed the JS plugins from `oxlint.config.ts`, and `doctor` and `upgrade` skipped their packages. A legacy config with single-quoted preset names in a string `extends` array is read the same way.
- 7d81f39: The rules `ultracite init` writes to `AGENTS.md`, `CLAUDE.md` and the other agent rules files now pass the formatter it sets up. The "Framework-Specific Guidance" section had no blank line between each bold label and the list under it, which Oxfmt and Prettier both reformat, so `ultracite check` failed on a freshly written rules file, and running `init` again undid what `ultracite fix` had changed. Run `ultracite init` again to pick up the corrected block.
- 4a32ea7: On the ESLint provider, `ultracite check` and `ultracite fix` now run Stylelint when the target is a quoted glob that isn't limited to stylesheets, such as `"src/**"` or `"**/*.{css,ts}"`. A glob with no extension was treated as a directory name and its wildcards escaped, and a glob ending in a non-style extension was dropped, so Stylelint matched nothing and the stylesheets went unlinted without a message. Those globs are now expanded and their `.css`, `.scss` and `.less` files passed to Stylelint. Directories, single files and globs that already name a style extension behave as before.
- c4c756e: `ultracite upgrade` no longer reinstalls `storybook` in an ESLint project that uses Storybook without the `storybook` preset. `storybook` is in the list of packages the preset installs because `eslint-plugin-storybook` needs it as a peer, and `upgrade` reinstalls every listed package the project already has, so a project on an older Storybook major had it moved to the version Ultracite pins. It is now reinstalled only when the config imports `ultracite/eslint/storybook` or the project has `eslint-plugin-storybook`.
- 3748eda: `ultracite init` no longer refuses to write into a directory whose name starts with two dots, such as `..apps`. The check that keeps writes inside the project treated any relative path beginning with `..` as leaving it, so `init` stopped with "Refusing to write outside project". Only a leading `..` path segment is rejected now.
