From a5a352254ff8a10d1eed5aae1c123597eefec2e3 Mon Sep 17 00:00:00 2001 From: Joe Clark <31087804+jc-clark@users.noreply.github.com> Date: Fri, 18 Oct 2024 11:39:16 -0700 Subject: [PATCH] Update release-phases variables with new terminology (#52466) Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> Co-authored-by: Felicity Chapman --- .../about-billing-for-your-enterprise.md | 2 +- ...ing-your-configuration-of-default-setup.md | 4 +- ...analyzing-your-code-with-codeql-queries.md | 2 +- .../customizing-analysis-with-codeql-packs.md | 2 +- .../style-guide.md | 61 +++++++++++++++++++ .../github-copilot-features.md | 2 +- .../using-copilot-text-completion.md | 2 +- .../filtering-projects.md | 2 +- .../searching-discussions.md | 2 +- .../section-choosing-the-runner-for-a-job.md | 2 +- .../reusables/actions/larger-runners-table.md | 4 +- .../actions/supported-github-runners.md | 4 +- .../copilot/about-copilot-chat-in-mobile.md | 2 +- .../rai/copilot/copilot-chat-dotcom-beta.md | 2 +- .../copilot-chat-ide-leveraging-web-search.md | 4 +- .../generic-secret-detection-ai.md | 4 +- data/ui.yml | 2 +- data/variables/release-phases.yml | 16 ++--- src/fixtures/fixtures/data/ui.yml | 2 +- 19 files changed, 91 insertions(+), 30 deletions(-) diff --git a/content/billing/using-the-billing-platform/about-billing-for-your-enterprise.md b/content/billing/using-the-billing-platform/about-billing-for-your-enterprise.md index 822478ed00..86e664a483 100644 --- a/content/billing/using-the-billing-platform/about-billing-for-your-enterprise.md +++ b/content/billing/using-the-billing-platform/about-billing-for-your-enterprise.md @@ -59,7 +59,7 @@ Administrators for your enterprise account on {% data variables.product.prodname ## How do I know which billing platform I'm using? -You have access to the new billing platform if you have an enterprise account, or if you are part of an organization owned by an enterprise account, created after June 2, 2024. Enterprises that participated in the beta program also have access to the new billing platform. See "[AUTOTITLE](/billing/using-the-new-billing-platform/about-the-new-billing-platform-for-enterprises)." +You have access to the new billing platform if you have an enterprise account, or if you are part of an organization owned by an enterprise account, created after June 2, 2024. Enterprises that participated in the {% data variables.release-phases.private_preview %} also have access to the new billing platform. See "[AUTOTITLE](/billing/using-the-new-billing-platform/about-the-new-billing-platform-for-enterprises)." {% data reusables.billing.new-billing-platform-permissions %} diff --git a/content/code-security/code-scanning/managing-your-code-scanning-configuration/editing-your-configuration-of-default-setup.md b/content/code-security/code-scanning/managing-your-code-scanning-configuration/editing-your-configuration-of-default-setup.md index bd4687e60b..d412a8ede0 100644 --- a/content/code-security/code-scanning/managing-your-code-scanning-configuration/editing-your-configuration-of-default-setup.md +++ b/content/code-security/code-scanning/managing-your-code-scanning-configuration/editing-your-configuration-of-default-setup.md @@ -18,7 +18,7 @@ topics: After running an initial analysis of your code with default setup, you may need to make changes to your configuration to better meet your code security needs. For existing configurations of default setup, you can edit: * Which languages default setup will analyze. * The query suite run during analysis. For more information on the available query suites, see "[AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/codeql-query-suites)."{% ifversion codeql-threat-models %} -* The threat models (beta) to use for analysis. Your choice of threat model determines which sources of tainted data are treated as a risk to your application. During the {% data variables.release-phases.public_preview %}, threat models are supported only for analysis of {% data variables.code-scanning.code_scanning_threat_model_support %}. For more information about threat models, see "[Including local sources of tainted data in default setup](#including-local-sources-of-tainted-data-in-default-setup)." +* The threat models ({% data variables.release-phases.public_preview %}) to use for analysis. Your choice of threat model determines which sources of tainted data are treated as a risk to your application. During the {% data variables.release-phases.public_preview %}, threat models are supported only for analysis of {% data variables.code-scanning.code_scanning_threat_model_support %}. For more information about threat models, see "[Including local sources of tainted data in default setup](#including-local-sources-of-tainted-data-in-default-setup)." {% endif %} {% ifversion codeql-model-packs %} @@ -38,7 +38,7 @@ If you need to change any other aspects of your {% data variables.product.prodna 1. In the "{% data variables.product.prodname_codeql %} default configuration" window, click {% octicon "pencil" aria-hidden="true" %} **Edit**. 1. Optionally, in the "Languages" section, select or deselect languages for analysis. 1. Optionally, in the "Query suite" row of the "Scan settings" section, select a different query suite to run against your code.{% ifversion codeql-threat-models %} -1. (Beta) Optionally, in the "Threat model" row of the "Scan settings" section, select **Remote and local sources**. +1. ({% data variables.release-phases.public_preview_caps %}) Optionally, in the "Threat model" row of the "Scan settings" section, select **Remote and local sources**. {% endif %} 1. To update your configuration, as well as run an initial analysis of your code with the new configuration, click **Save changes**. All future analyses will use your new configuration. diff --git a/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/analyzing-your-code-with-codeql-queries.md b/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/analyzing-your-code-with-codeql-queries.md index ca20d5dd6f..2a59ef1fa5 100644 --- a/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/analyzing-your-code-with-codeql-queries.md +++ b/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/analyzing-your-code-with-codeql-queries.md @@ -74,7 +74,7 @@ You must specify ``, `--format`, and `--output`. You can specify addit | --download | {% octicon "x" aria-label="Optional" %} | Use if some of your {% data variables.product.prodname_codeql %} query packs are not yet on disk and need to be downloaded before running queries. | | --threads | {% octicon "x" aria-label="Optional" %} | Use if you want to use more than one thread to run queries. The default value is `1`. You can specify more threads to speed up query execution. To set the number of threads to the number of logical processors, specify `0`. | | --verbose | {% octicon "x" aria-label="Optional" %} | Use to get more detailed information about the analysis process and diagnostic data from the database creation process. | -| --threat-model | {% octicon "x" aria-label="Optional" %} | (Beta) Use to add threat models to configure additional sources in your {% data variables.product.prodname_codeql %} analysis. During the {% data variables.release-phases.public_preview %}, threat models are supported only by Java analysis. For more information, see "[AUTOTITLE](/code-security/codeql-cli/codeql-cli-manual/database-analyze#--threat-modelname)." | +| --threat-model | {% octicon "x" aria-label="Optional" %} | ({% data variables.release-phases.public_preview_caps %}) Use to add threat models to configure additional sources in your {% data variables.product.prodname_codeql %} analysis. During the {% data variables.release-phases.public_preview %}, threat models are supported only by Java analysis. For more information, see "[AUTOTITLE](/code-security/codeql-cli/codeql-cli-manual/database-analyze#--threat-modelname)." | {% note %} diff --git a/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/customizing-analysis-with-codeql-packs.md b/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/customizing-analysis-with-codeql-packs.md index 4302e1e6ec..e04a64042e 100644 --- a/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/customizing-analysis-with-codeql-packs.md +++ b/content/code-security/codeql-cli/getting-started-with-the-codeql-cli/customizing-analysis-with-codeql-packs.md @@ -49,7 +49,7 @@ You can publish {% data variables.product.prodname_codeql %} packs that you have ## Downloading and using {% data variables.product.prodname_codeql %} query packs -The {% data variables.product.prodname_codeql_cli %} bundle includes queries that are maintained by {% data variables.product.company_short %} experts, security researchers, and community contributors. If you want to run queries developed by other organizations, {% data variables.product.prodname_codeql %} query packs provide an efficient and reliable way to download and run queries{% ifversion codeql-model-packs %}, while model packs (beta) can be used to expand {% data variables.product.prodname_code_scanning %} analysis to recognize libraries and frameworks that are not supported by default{% endif %}. For more information about query packs, see "[AUTOTITLE](/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning-with-codeql#about-codeql-queries)." {% ifversion codeql-model-packs %} For information about writing your own model packs, see "[AUTOTITLE](/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/creating-and-working-with-codeql-packs#creating-a-model-pack)."{% endif %} +The {% data variables.product.prodname_codeql_cli %} bundle includes queries that are maintained by {% data variables.product.company_short %} experts, security researchers, and community contributors. If you want to run queries developed by other organizations, {% data variables.product.prodname_codeql %} query packs provide an efficient and reliable way to download and run queries{% ifversion codeql-model-packs %}, while model packs ({% data variables.release-phases.public_preview %}) can be used to expand {% data variables.product.prodname_code_scanning %} analysis to recognize libraries and frameworks that are not supported by default{% endif %}. For more information about query packs, see "[AUTOTITLE](/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning-with-codeql#about-codeql-queries)." {% ifversion codeql-model-packs %} For information about writing your own model packs, see "[AUTOTITLE](/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/creating-and-working-with-codeql-packs#creating-a-model-pack)."{% endif %} Before you can use a {% data variables.product.prodname_codeql %} query pack to analyze a database, you must download any packages you require from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}. This can be done either by using the `--download` flag as part of the `codeql database analyze` command, or running `codeql pack download`. If a package is not publicly available, you will need to use a {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} to authenticate. For more information and an example, see "[AUTOTITLE](/code-security/codeql-cli/getting-started-with-the-codeql-cli/uploading-codeql-analysis-results-to-github#uploading-results-to-github)." diff --git a/content/contributing/style-guide-and-content-model/style-guide.md b/content/contributing/style-guide-and-content-model/style-guide.md index 1defdb6ef6..f6677ef846 100644 --- a/content/contributing/style-guide-and-content-model/style-guide.md +++ b/content/contributing/style-guide-and-content-model/style-guide.md @@ -923,7 +923,12 @@ Each release note in a set describes one of the following changes. * [Bug fixes](#bug-fixes): fixes to flaws or unexpected behavior * [Changes](#changes): notable changes to past behavior * [Known issues](#known-issues): issues that {% data variables.product.company_short %} has identified, but cannot or has not yet prioritized +{%- ifversion ghes < 3.16 %} * [Deprecations](#deprecations): removal of a feature or behavior +{%- else %} +* [Closing down](#closing-down): the process of being retired and should no longer be relied upon for future work +* [Retired](#retired): end of a product or feature lifecycle +{%- endif %} * [Errata](#errata): correction to inaccurate release note or documentation You can also review guidelines for updating release notes in "[Adding or updating a release note](#adding-or-updating-a-release-note)" and "[Removing a release note](#removing-a-release-note)." @@ -1066,6 +1071,8 @@ A release note for a known issue answers the following questions. * > After an administrator begins a configuration run, a `No such object error` may occur during the validation phase for the Notebook and Viewscreen services. This error can be ignored as the services should still correctly start. +{% ifversion ghes < 3.16 %} + ### Deprecations A deprecation release note summarizes a behavior or feature that {% data variables.product.company_short %} has removed or plans to remove. Generally, notes for deprecations are only part of feature releases. @@ -1092,6 +1099,60 @@ A release note for a deprecation answers the following questions. * > Commit comments, which are comments that users add directly to a commit outside of a pull request, no longer appear in the pull request timeline. Users could not reply to or resolve these comments. The Timeline events REST API and the GraphQL API's `PullRequest` object also no longer return commit comments. +{% else %} + +### Closing down + +A release note for a feature that is closing down summarizes a behavior or feature that {% data variables.product.github %} plans to remove. These features are still available for production use and come with the associated support SLAs and technical support obligations. However, they are in the process of being retired and should no longer be relied upon for future work. Closing down is a transitional stage where users are advised to stop using the feature and prepare for its retirement. + +#### Writing release notes features that are closing down + +A release note for a feature that is closing down answers the following questions. + +1. Does this existing functionality apply to me, with my role or access? +1. What is the functionality that's closing down? +1. If applicable, what replaces the closing down functionality? +1. If applicable, where can I read more? + +> _AUDIENCE_ (**1**) _DESCRIPTION OF CLOSING DOWN FUNCTIONALITY_ (**2**) _REPLACEMENT FUNCTIONALITY_ (**3**) For more information, see "[_ARTICLE TITLE_](/)" (**4**). + +* Notes are in the present tense, or the future tense for upcoming changes. If applicable, specify the upcoming release when the retirement will occur. +* To reduce repetition and unnecessary words, "now" is usually implied. +* To clarify actors and impact, avoid passive language when possible. +* Categorize each feature in a section, under a feature heading. + +#### Examples of release notes for features that are closing down + +* > **Closing down**: In {% data variables.product.prodname_ghe_server %} 3.8 and later, to ensure instance security, unsecure algorithms will be disabled for SSH connections to the administrative shell. + +* > Commit comments, which are comments that users add directly to a commit outside of a pull request, no longer appear in the pull request timeline. Users could not reply to or resolve these comments. The Timeline events REST API and the GraphQL API's `PullRequest` object also no longer return commit comments. + +### Retired + +Retired products or features are no longer available for new customers, marketed, supported, or documented. At this stage, the product is effectively discontinued, and no new development or fixes will be provided. The only support for retired products may come from existing commitments, such as those required for previously released versions of {% data variables.product.prodname_ghe_server %}. Retiring marks the official end of a product or feature's lifecycle, with no further updates, bug fixes, or user support, signaling a complete transition to newer tools or services. + +#### Writing release notes for retired features + +A release note for a retired feature answers the following questions. + +1. Does this functionality apply to me, with my role or access? +1. What is the functionality that's retired? +1. If applicable, what replaces the retired functionality? +1. If applicable, where can I read more? + +> _AUDIENCE_ (**1**) _DESCRIPTION OF RETIRED FUNCTIONALITY_ (**2**) _REPLACEMENT FUNCTIONALITY_ (**3**) For more information, see "[_ARTICLE TITLE_](/)" (**4**). + +* Notes are in the present tense. +* To reduce repetition and unnecessary words, "now" is usually implied. +* To clarify actors and impact, avoid passive language when possible. +* Categorize each feature in a section, under a feature heading. + +#### Examples of release notes for retired features + +* > **Retired**: {% data variables.product.github %} no longer supports required workflows for {% data variables.product.prodname_actions %} in {% data variables.product.prodname_ghe_server %} 3.11 and later. Use repository rulesets instead. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets#require-workflows-to-pass-before-merging)." + +{% endif %} + ### Errata Errata corrects inaccurate information previously published in the release notes or documentation for a release. diff --git a/content/copilot/about-github-copilot/github-copilot-features.md b/content/copilot/about-github-copilot/github-copilot-features.md index dc185efb73..92df92fc00 100644 --- a/content/copilot/about-github-copilot/github-copilot-features.md +++ b/content/copilot/about-github-copilot/github-copilot-features.md @@ -30,7 +30,7 @@ A chat-like interface in the terminal, where you can ask questions about the com AI-generated summaries of the changes that were made in a pull request, which files they impact, and what a reviewer should focus on when they conduct their review. -### {% data variables.product.prodname_copilot_autocomplete_pr %} (beta) +### {% data variables.product.prodname_copilot_autocomplete_pr %} ({% data variables.release-phases.public_preview %}) AI-generated text completion to help you write pull request descriptions quickly and accurately. diff --git a/content/copilot/using-github-copilot/using-copilot-text-completion.md b/content/copilot/using-github-copilot/using-copilot-text-completion.md index f8c85a422e..e133cfad4a 100644 --- a/content/copilot/using-github-copilot/using-copilot-text-completion.md +++ b/content/copilot/using-github-copilot/using-copilot-text-completion.md @@ -35,4 +35,4 @@ You can use {% data variables.product.prodname_copilot_autocomplete_pr %} in the You can disable or enable {% data variables.product.prodname_copilot_autocomplete_pr %} for your pull request descriptions. Your preference will be saved for future pull requests. 1. On {% data variables.product.github %}, create a pull request. -1. At the top of the description field, select {% octicon "copilot" aria-hidden="true" %} then hover over **Autocomplete (Beta)**, and click **Disabled** or **Enabled**. +1. At the top of the description field, select {% octicon "copilot" aria-hidden="true" %} then hover over **Autocomplete ({% data variables.release-phases.public_preview_caps %})**, and click **Disabled** or **Enabled**. diff --git a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md index edb96e107a..71d79e160a 100644 --- a/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md +++ b/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md @@ -39,7 +39,7 @@ You can use filters to produce views for very specific purposes. For example, yo | label:LABEL | **label:bug** will show items with the "bug" label applied. | field:VALUE | **status:done** will show items with the "status" field set to "done." | reviewers:USERNAME | **reviewers:octocat** will show items that have been reviewed by @octocat. -| milestone:"MILESTONE" | **milestone:"Beta release"** will show items assigned to the "Beta release" milestone. +| milestone:"MILESTONE" | **milestone:"QA release"** will show items assigned to the "QA release" milestone. ## Combining filters diff --git a/content/search-github/searching-on-github/searching-discussions.md b/content/search-github/searching-on-github/searching-discussions.md index 04405af34a..d61a90af82 100644 --- a/content/search-github/searching-on-github/searching-discussions.md +++ b/content/search-github/searching-on-github/searching-discussions.md @@ -107,7 +107,7 @@ You can use the `involves` qualifier to find discussions that involve a certain | Qualifier | Example | | :- | :- | | involves:USERNAME | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** matches discussions either @becca or @octocat are involved in. -| `in:body` involves:USERNAME | [**NOT {% data variables.release-phases.public_preview %} in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "beta" in the body. +| `in:body` involves:USERNAME | [**NOT free in:body involves:becca**](https://github.com/search?q=NOT+free+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "free" in the body. ## Search by number of comments diff --git a/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md b/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md index 278e9330b8..4144e65915 100644 --- a/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md +++ b/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md @@ -82,7 +82,7 @@ The windows-latest label currently uses the Windows 2022 runner ima -macos-latest, macos-15 [Beta], macos-14, macos-13, macos-12 +macos-latest, macos-15 [{% data variables.release-phases.public_preview_caps %}], macos-14, macos-13, macos-12 The macos-latest workflow label currently uses the macOS 14 runner image. diff --git a/data/reusables/actions/larger-runners-table.md b/data/reusables/actions/larger-runners-table.md index 1b826ae89d..8e941e6b43 100644 --- a/data/reusables/actions/larger-runners-table.md +++ b/data/reusables/actions/larger-runners-table.md @@ -1,4 +1,4 @@ | Runner Size | Architecture| Processor (CPU)| Memory (RAM) | Storage (SSD) | Workflow label | | ------------| ------------| -------------- | ------------- | ------------- |--------------------------------------------------------------------------------------------------------------------------------------------------| -| Large | Intel | 12 | 30 GB | 14 GB | macos-latest-large, macos-12-large, macos-13-large, macos-14-large [latest], macos-15-large [Beta] | -| XLarge | arm64 (M1) | 6 (+ 8 GPU hardware acceleration) | 14 GB | 14 GB | macos-latest-xlarge, macos-13-xlarge , macos-14-xlarge [latest], macos-15-xlarge [Beta] | +| Large | Intel | 12 | 30 GB | 14 GB | macos-latest-large, macos-12-large, macos-13-large, macos-14-large [latest], macos-15-large [{% data variables.release-phases.public_preview_caps %}] | +| XLarge | arm64 (M1) | 6 (+ 8 GPU hardware acceleration) | 14 GB | 14 GB | macos-latest-xlarge, macos-13-xlarge , macos-14-xlarge [latest], macos-15-xlarge [{% data variables.release-phases.public_preview_caps %}] | diff --git a/data/reusables/actions/supported-github-runners.md b/data/reusables/actions/supported-github-runners.md index 377229befc..7c4f245153 100644 --- a/data/reusables/actions/supported-github-runners.md +++ b/data/reusables/actions/supported-github-runners.md @@ -62,7 +62,7 @@ For public repositories, jobs using the workflow labels shown in the table below macos-latest, macos-14, - macos-15 [Beta] + macos-15 [{% data variables.release-phases.public_preview_caps %}] @@ -133,7 +133,7 @@ For {% ifversion ghec %}internal and{% endif %} private repositories, jobs using macos-latest, macos-14, - macos-15 [Beta] + macos-15 [{% data variables.release-phases.public_preview_caps %}] diff --git a/data/reusables/rai/copilot/about-copilot-chat-in-mobile.md b/data/reusables/rai/copilot/about-copilot-chat-in-mobile.md index d1d7a8eaf2..8e8f099b98 100644 --- a/data/reusables/rai/copilot/about-copilot-chat-in-mobile.md +++ b/data/reusables/rai/copilot/about-copilot-chat-in-mobile.md @@ -21,7 +21,7 @@ The response generated by {% data variables.product.prodname_copilot_chat_short The options available to you in {% data variables.product.prodname_copilot_mobile_short %} vary depending on the {% data variables.product.prodname_copilot %} plan you are using. * Only people with a {% data variables.product.prodname_copilot_enterprise %} subscription can access and have conversations using the data from private indexed repositories. -* If you have a {% data variables.product.prodname_copilot_enterprise %} subscription and you have enabled Bing search integration (beta), {% data variables.product.prodname_copilot_mobile_short %} may respond using information based on the results of a Bing search. For information on how to enable or disable Bing search integration, see "[AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} +* If you have a {% data variables.product.prodname_copilot_enterprise %} subscription and you have enabled Bing search integration ({% data variables.release-phases.public_preview %}), {% data variables.product.prodname_copilot_mobile_short %} may respond using information based on the results of a Bing search. For information on how to enable or disable Bing search integration, see "[AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-policies-and-features-for-copilot-in-your-enterprise){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} * In addition to general coding conversations or conversations about a single file, people with a {% data variables.product.prodname_copilot_individuals_short %} subscription have the ability to discuss top popular public repositories using embeddings. If you do not have a {% data variables.product.prodname_copilot %} subscription, you can purchase a {% data variables.product.prodname_copilot_individuals_short %} subscription directly in the iOS version of {% data variables.product.prodname_mobile %}, or in the Google Play Store for the Android version of {% data variables.product.prodname_mobile %}. diff --git a/data/reusables/rai/copilot/copilot-chat-dotcom-beta.md b/data/reusables/rai/copilot/copilot-chat-dotcom-beta.md index e7aae83db0..3d11b9ce08 100644 --- a/data/reusables/rai/copilot/copilot-chat-dotcom-beta.md +++ b/data/reusables/rai/copilot/copilot-chat-dotcom-beta.md @@ -1 +1 @@ -{% data variables.product.prodname_copilot_chat %} is currently in beta for users with a {% data variables.product.prodname_copilot_individuals_short %} or {% data variables.product.prodname_copilot_business_short %} subscription. +{% data variables.product.prodname_copilot_chat %} is currently in {% data variables.release-phases.public_preview %} for users with a {% data variables.product.prodname_copilot_individuals_short %} or {% data variables.product.prodname_copilot_business_short %} subscription. diff --git a/data/reusables/rai/copilot/copilot-chat-ide-leveraging-web-search.md b/data/reusables/rai/copilot/copilot-chat-ide-leveraging-web-search.md index b493506aa1..4289c1c7e9 100644 --- a/data/reusables/rai/copilot/copilot-chat-ide-leveraging-web-search.md +++ b/data/reusables/rai/copilot/copilot-chat-ide-leveraging-web-search.md @@ -1,8 +1,8 @@ ### Leveraging a web search to answer a question > [!NOTE] -> * Bing search integration in {% data variables.product.prodname_copilot_chat_short %} is currently in beta and is subject to change. -> * The `@github` chat participant in {% data variables.product.prodname_vscode_shortname %} and {% data variables.product.prodname_vs %} is currently in preview and is subject to change. For more information, see "[Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/en-us/support/legal/preview-supplemental-terms)." +> * Bing search integration in {% data variables.product.prodname_copilot_chat_short %} is currently in {% data variables.release-phases.public_preview %} and is subject to change. +> * The `@github` chat participant in {% data variables.product.prodname_vscode_shortname %} and {% data variables.product.prodname_vs %} is currently in {% data variables.release-phases.public_preview %} and is subject to change. For more information, see "[Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/en-us/support/legal/preview-supplemental-terms)." When you use the `@github` chat participant, {% data variables.product.prodname_copilot_chat %} can use a Bing search to help answer your question if this has been enabled by your administrator. diff --git a/data/reusables/rai/secret-scanning/generic-secret-detection-ai.md b/data/reusables/rai/secret-scanning/generic-secret-detection-ai.md index a97d8ae970..d6f62c34cb 100644 --- a/data/reusables/rai/secret-scanning/generic-secret-detection-ai.md +++ b/data/reusables/rai/secret-scanning/generic-secret-detection-ai.md @@ -2,9 +2,9 @@ {% note %} **Note:** {% ifversion secret-scanning-ai-generic-secret-detection %} -Generic secret detection for {% data variables.product.prodname_secret_scanning %} is in beta. Functionality and documentation are subject to change. During this phase, generic secret detection is limited to looking for passwords in source code. +Generic secret detection for {% data variables.product.prodname_secret_scanning %} is in {% data variables.release-phases.public_preview %}. Functionality and documentation are subject to change. During this phase, generic secret detection is limited to looking for passwords in source code. {% elsif fpt %} -Generic secret detection for {% data variables.product.prodname_secret_scanning %} is in beta. Functionality and documentation are subject to change. The feature is available for enterprise accounts that use {% data variables.product.prodname_GH_advanced_security %} on {% data variables.product.prodname_ghe_cloud %}. +Generic secret detection for {% data variables.product.prodname_secret_scanning %} is in {% data variables.release-phases.public_preview %}. Functionality and documentation are subject to change. The feature is available for enterprise accounts that use {% data variables.product.prodname_GH_advanced_security %} on {% data variables.product.prodname_ghe_cloud %}. {% endif %} {% endnote %} diff --git a/data/ui.yml b/data/ui.yml index d52e803c66..e2607bd191 100644 --- a/data/ui.yml +++ b/data/ui.yml @@ -7,7 +7,7 @@ header: release_candidate: # The version name is rendered before the below text via includes/header-notification.html ' is currently available as a release candidate.' - early_access: 📣 Please do not share this URL publicly. This page contains content about an early access feature. + early_access: 📣 Please do not share this URL publicly. This page contains content about a private preview feature. release_notes_use_latest: Please use the latest release for the latest security, performance, and bug fixes. # GHES release notes ghes_release_notes_upgrade_patch_only: 📣 This is not the latest patch release of Enterprise Server. diff --git a/data/variables/release-phases.yml b/data/variables/release-phases.yml index 5b50818d05..b1d0f5052f 100644 --- a/data/variables/release-phases.yml +++ b/data/variables/release-phases.yml @@ -2,25 +2,25 @@ # For reference: https://github.com/github/docs-team/issues/4302 public_preview: >- - {% ifversion ghes < 3.16 %}beta{% else %}beta{% endif %} + {% ifversion ghes < 3.16 %}beta{% else %}public preview{% endif %} public_preview_caps: >- - {% ifversion ghes < 3.16 %}Beta{% else %}Beta{% endif %} + {% ifversion ghes < 3.16 %}Beta{% else %}Public preview{% endif %} private_preview: >- - {% ifversion ghes < 3.16 %}private beta{% else %}private beta{% endif %} + {% ifversion ghes < 3.16 %}private beta{% else %}private preview{% endif %} private_preview_caps: >- - {% ifversion ghes < 3.16 %}Private beta{% else %}Private beta{% endif %} + {% ifversion ghes < 3.16 %}Private beta{% else %}Private preview{% endif %} closing_down: >- - {% ifversion ghes < 3.16 %}deprecated{% else %}deprecated{% endif %} + {% ifversion ghes < 3.16 %}deprecated{% else %}closing down{% endif %} closing_down_caps: >- - {% ifversion ghes < 3.16 %}Deprecated{% else %}Deprecated{% endif %} + {% ifversion ghes < 3.16 %}Deprecated{% else %}Closing down{% endif %} retired: >- - {% ifversion ghes < 3.16 %}sunset{% else %}sunset{% endif %} + {% ifversion ghes < 3.16 %}sunset{% else %}retired{% endif %} retired_caps: >- - {% ifversion ghes < 3.16 %}Sunset{% else %}Sunset{% endif %} + {% ifversion ghes < 3.16 %}Sunset{% else %}Retired{% endif %} diff --git a/src/fixtures/fixtures/data/ui.yml b/src/fixtures/fixtures/data/ui.yml index d52e803c66..e2607bd191 100644 --- a/src/fixtures/fixtures/data/ui.yml +++ b/src/fixtures/fixtures/data/ui.yml @@ -7,7 +7,7 @@ header: release_candidate: # The version name is rendered before the below text via includes/header-notification.html ' is currently available as a release candidate.' - early_access: 📣 Please do not share this URL publicly. This page contains content about an early access feature. + early_access: 📣 Please do not share this URL publicly. This page contains content about a private preview feature. release_notes_use_latest: Please use the latest release for the latest security, performance, and bug fixes. # GHES release notes ghes_release_notes_upgrade_patch_only: 📣 This is not the latest patch release of Enterprise Server.