From c1fdb9c46d5f5166fb42380bf63fd71ab9db4647 Mon Sep 17 00:00:00 2001 From: Zanie Blue Date: Thu, 12 Oct 2023 17:35:39 -0500 Subject: [PATCH] Add unsafe fixes entry to breaking changes (#7930) --- BREAKING_CHANGES.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/BREAKING_CHANGES.md b/BREAKING_CHANGES.md index f79222140f..a565f6547b 100644 --- a/BREAKING_CHANGES.md +++ b/BREAKING_CHANGES.md @@ -2,7 +2,16 @@ ## 0.1.0 -### Remove formatter-conflicting rules from the default rule set +### Unsafe fixes are not applied by default ([#7769](https://github.com/astral-sh/ruff/pull/7769)) + +Ruff labels fixes as "safe" and "unsafe". The meaning and intent of your code will be retained when applying safe +fixes, but the meaning could be changed when applying unsafe fixes. Previously, unsafe fixes were always displayed +and applied when fixing was enabled. Now, unsafe fixes are hidden by default and not applied. The `--unsafe-fixes` +flag or `unsafe-fixes` configuration option can be used to enable unsafe fixes. + +See the [docs](https://docs.astral.sh/ruff/configuration/#fix-safety) for details. + +### Remove formatter-conflicting rules from the default rule set ([#7900](https://github.com/astral-sh/ruff/pull/7900)) Previously, Ruff enabled all implemented rules in Pycodestyle (`E`) by default. Ruff now only includes the Pycodestyle prefixes `E4`, `E7`, and `E9` to exclude rules that conflict with automatic formatters. Consequently,