Stabilise redirected-noqa (RUF101) (#12869)

Author: AlexWaygood

crates/ruff_linter/src/codes.rs

@@ -959,7 +959,7 @@ pub fn code_to_rule(linter: Linter, code: &str) -> Option<(RuleGroup, Rule)> {
         (Ruff, "030") => (RuleGroup::Preview, rules::ruff::rules::AssertWithPrintMessage),
         (Ruff, "031") => (RuleGroup::Preview, rules::ruff::rules::IncorrectlyParenthesizedTupleInSubscript),
         (Ruff, "100") => (RuleGroup::Stable, rules::ruff::rules::UnusedNOQA),
-        (Ruff, "101") => (RuleGroup::Preview, rules::ruff::rules::RedirectedNOQA),
+        (Ruff, "101") => (RuleGroup::Stable, rules::ruff::rules::RedirectedNOQA),
 
         (Ruff, "200") => (RuleGroup::Stable, rules::ruff::rules::InvalidPyprojectToml),
         #[cfg(any(feature = "test-rules", test))]

crates/ruff_linter/src/rules/ruff/rules/redirected_noqa.rs

@@ -9,8 +9,8 @@ use crate::rule_redirects::get_redirect_target;
 /// Checks for `noqa` directives that use redirected rule codes.
 ///
 /// ## Why is this bad?
-/// When a rule code has been redirected, the implication is that the rule has
-/// been deprecated in favor of another rule or code. To keep the codebase
+/// When one of Ruff's rule codes has been redirected, the implication is that the rule has
+/// been deprecated in favor of another rule or code. To keep your codebase
 /// consistent and up-to-date, prefer the canonical rule code over the deprecated
 /// code.
 ///