Fix outdated-release-phase-terminology warnings (#58306)

Co-authored-by: Copilot <[email protected]>

Author: jc-clark

content/admin/managing-iam/provisioning-user-accounts-with-scim/user-provisioning-with-scim-on-ghes.md

@@ -41,7 +41,7 @@ The following IdPs are partner IdPs. They offer an application that you can use
 
 * Microsoft Entra ID
 * Okta
-* PingFederate (beta)
+* PingFederate ({% data variables.release-phases.public_preview %})
 
 When you use a single partner IdP for both authentication and provisioning, {% data variables.product.company_short %} provides support for the application on the partner IdP and the IdP's integration with {% data variables.product.prodname_dotcom %}. Support for PingFederate is in {% data variables.release-phases.public_preview %}.
 

content/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/publishing-and-using-codeql-packs.md

@@ -352,7 +352,7 @@ The following properties are supported in `qlpack.yml` files.
 
 #### `libraryPathDependencies`
 
-* Optional, deprecated. Use the `dependencies` property instead.
+* Optional, {% data variables.release-phases.closing_down %}. Use the `dependencies` property instead.
 * Previously used to define the names of any {% data variables.product.prodname_codeql %} packs that this {% data variables.product.prodname_codeql %} pack depends on, as an array. This gives the pack access to any libraries, database schema, and query suites defined in the dependency. For example:
 
   ```yaml

content/code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/using-the-codeql-model-editor.md

@@ -44,7 +44,7 @@ The rest of this article covers the practical aspects of modelling dependencies
 
 1. In the "Databases" view, select the {% data variables.product.prodname_codeql %} database that you want to model from.
 
-1. In the {% data variables.product.prodname_codeql %} "Method Modeling" view, click **Start modeling** to display the model editor. Alternatively, use the {% data variables.product.prodname_vscode_command_palette_shortname %} to run the **{% data variables.product.prodname_codeql %}: Open Model Editor (Beta)** command.
+1. In the {% data variables.product.prodname_codeql %} "Method Modeling" view, click **Start modeling** to display the model editor. Alternatively, use the {% data variables.product.prodname_vscode_command_palette_shortname %} to run the **{% data variables.product.prodname_codeql %}: Open Model Editor (Beta)** command. <!-- markdownlint-disable-line outdated-release-phase-terminology --> <!-- "Beta" is in the name of the command in the VS Code extension -->
 
 1. The {% data variables.product.prodname_codeql %} model editor runs a series of telemetry queries to identify APIs in the code, and the editor is displayed in a new tab.
 

content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md

@@ -828,6 +828,8 @@ New version `2.0.0`
 
 ### Versioning tags
 
+<!-- markdownlint-disable outdated-release-phase-terminology -->
+
 * Represent stages in the software release lifecycle, such as alpha, beta, and stable versions.
 * Allow publishers to distribute their packages more effectively.
 * Indicate the stability of a version and communicate what users should expect in terms of features and stability.
@@ -849,6 +851,8 @@ New version `2.0.0`
 * **`release`:** The official release version.
 * **`stable`:** The most reliable, production-ready version.
 
+<!-- markdownlint-enable outdated-release-phase-terminology -->
+
 {% endif %}
 
 ## Top-level `registries` key

content/copilot/how-tos/use-copilot-for-common-tasks/use-copilot-in-the-cli.md

@@ -22,6 +22,6 @@ category:
   - Author and optimize with Copilot
 ---
 
-# Replacing the deprecated {% data variables.product.prodname_copilot_short %} extension
+# Replacing the {% data variables.release-phases.retired %} {% data variables.product.prodname_copilot_short %} extension
 
-The {% data variables.product.prodname_copilot %} extension for {% data variables.product.prodname_cli %} has been deprecated. It has been replaced by the new {% data variables.copilot.copilot_cli %}. See [AUTOTITLE](/copilot/concepts/agents/about-copilot-cli).
+The {% data variables.product.prodname_copilot %} extension for {% data variables.product.prodname_cli %} is {% data variables.release-phases.retired %}. It has been replaced by the new {% data variables.copilot.copilot_cli %}. See [AUTOTITLE](/copilot/concepts/agents/about-copilot-cli).

content/copilot/tutorials/enhance-agent-mode-with-mcp.md

@@ -93,7 +93,7 @@ First, you need to configure the MCP servers that you anticipate {% data variabl
 
 * **{% data variables.product.github %} MCP server**: Configure the {% data variables.product.github %} MCP server to enable {% data variables.product.prodname_copilot_short %} to access your repository, examine your codebase, research existing issues, create branches, and manage pull requests. See [AUTOTITLE](/copilot/customizing-copilot/using-model-context-protocol/using-the-github-mcp-server).
 
-* **Figma MCP server**: Configure the Figma MCP server to allow {% data variables.product.prodname_copilot_short %} to access design files that include accessibility specifications, such as color contrast requirements, focus states, and interaction patterns. See [Figma-Context-MCP](https://github.com/GLips/Figma-Context-MCP) or try out the [Dev Mode MCP server](https://help.figma.com/hc/en-us/articles/32132100833559-Guide-to-the-Dev-Mode-MCP-Server) in open beta.
+* **Figma MCP server**: Configure the Figma MCP server to allow {% data variables.product.prodname_copilot_short %} to access design files that include accessibility specifications, such as color contrast requirements, focus states, and interaction patterns. See [Figma-Context-MCP](https://github.com/GLips/Figma-Context-MCP) or try out the [Dev Mode MCP server](https://help.figma.com/hc/en-us/articles/32132100833559-Guide-to-the-Dev-Mode-MCP-Server).
 
 * **Playwright MCP server**: Set up the Playwright MCP server to enable {% data variables.product.prodname_copilot_short %} to write and run automated accessibility tests, including screen reader compatibility and keyboard navigation tests. See [mcp-playwright](https://github.com/executeautomation/mcp-playwright).
 

content/enterprise-onboarding/support-for-your-enterprise/understanding-support.md

@@ -28,7 +28,7 @@ Standard {% data variables.contact.github_support %} is provided as part of your
 
 * Escalation management: Dedicated escalation management ensures that complex issues are addressed promptly and efficiently, with a clear path for escalating critical incidents.
 
-* Early access to new features: Participation in beta programs and early access to new features allows you to stay ahead of the curve with the latest {% data variables.product.github %} innovations.
+* Early access to new features: Participation in {% data variables.release-phases.preview %} programs and early access to new features allows you to stay ahead of the curve with the latest {% data variables.product.github %} innovations.
 
 There are two support plans available with {% data variables.contact.premium_support %}:
 

content/integrations/how-tos/slack/customize-notifications.md

@@ -59,7 +59,7 @@ Branch filters allow you to filter commit notifications based on branch names. B
 |`/github subscribe owner/repo commits:feature/*`|Receive commit notifications for all branches that start with `feature/`.|
 |`/github subscribe owner/repo commits:*`|Receive commit notifications for all branches.|
 
->[!NOTE] You may have previously used the `commits:all` filter to receive commit notifications for all branches. This filter is now deprecated. To receive commit notifications for all branches, use the `commits:*` filter instead. If you have previously set up the `commits:all` filter, it will continue to work until you update your configuration to use the `commits:*` filter.
+>[!NOTE] You may have previously used the `commits:all` filter to receive commit notifications for all branches. This filter is {% data variables.release-phases.closing_down %}. To receive commit notifications for all branches, use the `commits:*` filter instead. If you have previously set up the `commits:all` filter, it will continue to work until you update your configuration to use the `commits:*` filter.
 
 ### Label filters for issue and pull request notifications
 

content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md

@@ -24,7 +24,7 @@ type: how_to
     * To create a new milestone, click **New Milestone**.
     * To edit a milestone, next to the milestone you want to edit, click **Edit**.
 
-       ![Screenshot of the list of milestones. Within the entry for the "beta release" milestone, a link, labeled "Edit," is outlined in dark orange.](/assets/images/help/repository/edit-milestone.png)
+       ![Screenshot of the list of milestones. Within the entry for the "beta release" milestone, a link, labeled "Edit," is outlined in dark orange.](/assets/images/help/repository/edit-milestone.png) <!-- markdownlint-disable-line outdated-release-phase-terminology -->
 1. Type the milestone's title, description, or other changes, and click **Create milestone** or **Save changes**. Milestones will render Markdown syntax. For more information about Markdown syntax, see [AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax).
 
 ## Deleting milestones
@@ -36,4 +36,4 @@ When you delete milestones, issues and pull requests are not affected.
 {% data reusables.project-management.milestones %}
 1. Next to the milestone you want to delete, click **Delete**.
 
-![Screenshot of the list of milestones for a repository. Within the entry for the "beta release" milestone, a red "Delete" link is outlined in orange.](/assets/images/help/repository/delete-milestone.png)
+![Screenshot of the list of milestones for a repository. Within the entry for the "beta release" milestone, a red "Delete" link is outlined in orange.](/assets/images/help/repository/delete-milestone.png) <!-- markdownlint-disable-line outdated-release-phase-terminology -->

content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md

@@ -64,10 +64,14 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
 
 1. Follow the interactive prompts. Alternatively, you can specify arguments to skip these prompts. For more information about possible arguments, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_release_create). For example, this command creates a prerelease with the specified title and notes.
 
+<!-- markdownlint-disable outdated-release-phase-terminology --> <!-- disable the outdated-release-phase-terminology rule since "beta" is part of the CLI command --> 
+
    ```shell
    gh release create v1.3.2 --title "v1.3.2 (beta)" --notes "this is a {% data variables.release-phases.public_preview %} release" --prerelease
    ```
 
+<!-- markdownlint-enable outdated-release-phase-terminology -->
+
 If you @mention any {% data variables.product.github %} users in the notes, the published release will include a **Contributors** section with an avatar list of all the mentioned users.
 
 {% endcli %}