All news
productsaas

Ruff v0.16.0 Expands Default Rules 7x for Python Devs

28 Jul 2026

Ruff, the Rust-based Python linter and formatter known for speed, has shipped v0.16.0 with a significant change to its default behavior: the number of rules enabled out of the box has jumped nearly 7x, from 59 to 413.

What changed

According to the release, Ruff's total rule library has grown from 708 to 968 rules, and the tool now stabilizes 12 rules out of preview status in this release — including AIR303, CPY001, FURB164, FURB192, ISC004, LOG004, PLE0304, PLR0917, PLR1708, RUF036, RUF063, and RUF068.

Beyond the default rule expansion, v0.16.0 introduces several new capabilities:

  • Markdown-embedded formatting: Ruff can now format Python code blocks that live inside Markdown files, useful for teams maintaining documentation alongside code.
  • Native suppression comments: A new ruff: ignore comment format lets developers suppress warnings on their own line.
  • Diff previews: Ruff now shows diffs for linter and formatter fixes directly in diagnostic output, giving developers a clearer view of proposed changes before applying them.
  • --add-ignore CLI flag: This new flag can automatically insert ruff: ignore comments, streamlining suppression across a codebase.

Why founders should care

For founders running Python-based products, this release carries a mix of upside and near-term friction that's worth budgeting for.

The expanded default rule set likely reduces the need for teams to manually configure extensive linting setups, which could modestly lower onboarding time for new engineers and shrink the surface area of custom config maintenance. At the same time, going from 59 to 413 default rules will plausibly surface new lint errors in codebases that previously passed clean — teams should expect some increase in CI failures immediately after upgrading, particularly in strict pipelines that previously ignored preview rules now stabilized into the default set.

The diff-preview and --add-ignore features seem likely to improve day-to-day developer experience by making it faster to review and suppress specific warnings, which could shave time off code review cycles. The Markdown formatting support may also offer a small efficiency gain for teams that keep code samples in docs synced with actual source — reducing the need for separate tooling.

What's not yet clear

The release notes don't explain why the default rule count increased so dramatically, nor do they detail whether existing project configurations will require adjustment to accommodate the new defaults. There's also no discussion of performance impact from enabling many more rules by default, and no migration guidance is provided for teams moving from earlier Ruff versions. Founders relying on Ruff in CI should plan to test the upgrade in a staging environment first, given these open questions.

Practical takeaway

Teams using Ruff should treat this as a budget-a-few-hours upgrade rather than a drop-in update: run it against your existing codebase before merging into main CI, review any newly surfaced lint errors, and check whether custom rule configurations need adjustment. The new suppression and diff-preview tooling should help make that review process faster once you're through the initial transition.

Sources