Remove case() support from GHES documentation (#62524)

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com>
Copilot-Session: 6f0bf5aa-920f-4478-83b2-d37f1b0a14ba

Author: 3 people

content/actions/reference/workflows-and-actions/expressions.md

@@ -275,6 +275,8 @@ Creates a hash for all `.rb` files in the `lib` directory at root level, includi
 
 `hashFiles('/lib/**/*.rb', '!/lib/foo/*.rb')`
 
+{% ifversion fpt or ghec %}
+
 ### case
 
 `case( pred1, val1, pred2, val2, ..., default )`
@@ -313,6 +315,8 @@ env:
 
 Sets `MY_ENV_VAR` based on the branch: `production` for `main`, `staging` for `staging`, `development` for branches starting with `feature/`, or `unknown` for all other branches.
 
+{% endif %}
+
 ## Status check functions
 
 You can use the following status check functions as expressions in `if` conditionals. A default status check of `success()` is applied unless you include one of these functions. For more information about `if` conditionals, see [AUTOTITLE](/actions/reference/workflows-and-actions/workflow-syntax#jobsjob_idif) and [AUTOTITLE](/actions/reference/workflows-and-actions/metadata-syntax#runsstepsif).

data/release-notes/enterprise-server/3-21/0-rc1.yml

@@ -135,9 +135,6 @@ sections:
         # https://github.com/github/releases/issues/7290
         - |
           When a workflow job is skipped because of an `if:` conditional, the job log now shows how the conditional expression was evaluated. This helps users verify whether a job was skipped for the expected reason or if there is an error in their workflow logic.
-        # https://github.com/github/releases/issues/7112
-        - |
-          {% data variables.product.prodname_actions %} expressions support a new `case` function that enables conditional logic (if/else if/else) directly within workflow expressions. Users can use the `case` function to select values based on conditions without needing to store that logic externally.
         # https://github.com/github/releases/issues/7074
         - |
           The {% data variables.product.prodname_actions %} workflow visualization page now supports rendering workflows with more than 300 jobs. Jobs are lazy loaded to prevent page errors when viewing large workflows. This feature is in public preview and subject to change.

data/release-notes/enterprise-server/3-21/0.yml

@@ -131,9 +131,6 @@ sections:
         # https://github.com/github/releases/issues/7290
         - |
           When a workflow job is skipped because of an `if:` conditional, the job log now shows how the conditional expression was evaluated. This helps users verify whether a job was skipped for the expected reason or if there is an error in their workflow logic.
-        # https://github.com/github/releases/issues/7112
-        - |
-          {% data variables.product.prodname_actions %} expressions support a new `case` function that enables conditional logic (if/else if/else) directly within workflow expressions. Users can use the `case` function to select values based on conditions without needing to store that logic externally.
         # https://github.com/github/releases/issues/7074
         - |
           The {% data variables.product.prodname_actions %} workflow visualization page now supports rendering workflows with more than 300 jobs. Jobs are lazy loaded to prevent page errors when viewing large workflows. This feature is in public preview and subject to change.
@@ -298,4 +295,6 @@ sections:
 
   errata:
     - |
-      These release notes previously included a note about pull requeset reviewers being able to comment on any line of a changed file, not just lines within the diff. The note was added prematurely and has been removed. We will republish it when the feature is ready. [Updated: 2026-06-23]
+      These release notes previously included a note about pull requeset reviewers being able to comment on any line of a changed file, not just lines within the diff. The note was added prematurely and has been removed. We will republish it when the feature is ready. [Updated: 2026-06-23]
+    - |
+      These release notes incorrecly indicated that the `case` function is supported in {% data variables.product.prodname_actions %} expressions. [Updated: 2026-07-30]