Astral's Ruff v0.16.0 Expands Default Rules Sevenfold, Triggering CI Failures
The Python linter's aggressive new defaults enable 413 rules out of the box, up from 59, forcing teams to choose between cleanup and configuration overrides.
Astral released Ruff v0.16.0 with a dramatic shift in philosophy: the high-performance Python linter now enables 413 rules by default, up from just 59 in previous versions. The change marks Ruff's transition from a conservative tool to an opinionated enforcement engine.
A Sevenfold Expansion
The default rule set now covers 413 of Ruff's 968 total rules, up from 708 total rules when the default set was last modified in v0.1.0. "Ruff now enables 413 rules by default, up from 59 in previous versions," Astral wrote in the release announcement.
For new projects, the stricter defaults promise immediate code quality gains. For existing codebases, the update delivers friction. Developer Simon Willison reported CI failures as projects without explicit lint selection rules now face hundreds of new warnings triggering overnight.
Markdown Support and Better Suppression
Beyond the rule expansion, v0.16.0 adds support for formatting Python code blocks embedded in Markdown files, eliminating the need to extract and format snippets separately. The release also introduces two new suppression comment syntaxes: `ruff: ignore` for line-level silencing and `ruff: file-ignore` for file-wide diagnostic suppression.
Astral improved the developer experience by displaying linter and formatter fixes as diffs directly in the `check` and `format --check` output, making it easier to preview changes before applying them.
The OpenAI Factor
Ruff, written in Rust, has become the de facto standard for Python linting and formatting, replacing fragmented toolchains built around Flake8, Black, and isort. Astral, the company behind Ruff, was acquired by OpenAI earlier this year, though the release notes do not indicate any direct influence from the acquisition on v0.16.0's feature set.
Migration Paths
Teams facing CI breakage have two options: expand their `ruff.toml` configuration to explicitly disable unwanted rules, or commit to the cleanup work the new defaults demand. The suppression comment improvements should help manage edge cases, but the fundamental choice remains whether to adopt Astral's new opinionated baseline or maintain a custom rule set.
The release underscores a broader trend in developer tooling: as linters mature, defaults shift from permissive to prescriptive. Ruff v0.16.0 makes that shift explicit, betting that short-term friction will yield long-term code quality gains.