From 1692fe23cbe707f7d9694ca2b2f10068194b36b5 Mon Sep 17 00:00:00 2001
From: Bryan Mishkin <698306+bmish@users.noreply.github.com>
Date: Tue, 9 Apr 2024 09:53:39 -0400
Subject: [PATCH] feat!: Add missing `deprecated`/`replacedBy` properties to
 `meta-property-ordering` rule (#320)

breaking: add missing deprecated/replacedBy properties to meta-property-ordering rule
---
 docs/rules/meta-property-ordering.md | 2 +-
 lib/rules/meta-property-ordering.js  | 2 ++
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/rules/meta-property-ordering.md b/docs/rules/meta-property-ordering.md
index 973138f5..e0215d83 100644
--- a/docs/rules/meta-property-ordering.md
+++ b/docs/rules/meta-property-ordering.md
@@ -12,7 +12,7 @@ This rule enforces that meta properties of a rule are placed in a consistent ord
 
 This rule has an array option:
 
-- `['type', 'docs', 'fixable', 'hasSuggestions', 'schema', 'messages', 'deprecated', 'replacedBy']` (default): The order that the properties of `meta` should be placed in.
+- `['type', 'docs', 'fixable', 'hasSuggestions', 'deprecated', 'replacedBy', 'schema', 'messages']` (default): The order that the properties of `meta` should be placed in.
 
 Examples of **incorrect** code for this rule:
 
diff --git a/lib/rules/meta-property-ordering.js b/lib/rules/meta-property-ordering.js
index d07215d3..46a91a59 100644
--- a/lib/rules/meta-property-ordering.js
+++ b/lib/rules/meta-property-ordering.js
@@ -45,6 +45,8 @@ module.exports = {
       'docs',
       'fixable',
       'hasSuggestions',
+      'deprecated',
+      'replacedBy',
       'schema',
       'messages',
     ];