Update available-rules-for-rulesets.md (#51822)

Co-authored-by: Joe Clark <31087804+jc-clark@users.noreply.github.com>

content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md

@@ -45,7 +45,6 @@ Before you can require a linear commit history, your repository must allow squas
 ## Require merge queue
 
 > [!NOTE]
-> * Configuring a merge queue via rulesets is in public beta and subject to change.
 > * This rule is not available for rulesets created at the organization level. For more information about creating rulesets at the repository level, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository)."
 
 You can require that merges must be performed with a merge queue at the repository level. For more information about merge queues, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue#about-merge-queues)."

content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository.md

@@ -104,12 +104,6 @@ You can view insights for rulesets to see how rulesets are affecting a repositor
 {%- ifversion repo-rules-merge-queue %}
 1. Optionally, review merge queue details for corresponding pull requests in the same merge group.
 
-    {% note %}
-
-    **Note:** The merge queue rule is in public beta and this interface is subject to change.
-
-    {% endnote %}
-
 {% endif %}
 
 {% endif %}

data/features/repo-rules-merge-queue.yml

@@ -3,4 +3,4 @@
 
 versions:
   ghec: '*'
-  ghes: '>=3.13'
+  ghes: '>=3.15'