diff --git a/descriptions-next/api.github.com/api.github.com.2022-11-28.json b/descriptions-next/api.github.com/api.github.com.2022-11-28.json
index 383f4a8580..d3f91531bc 100644
--- a/descriptions-next/api.github.com/api.github.com.2022-11-28.json
+++ b/descriptions-next/api.github.com/api.github.com.2022-11-28.json
@@ -64314,7 +64314,7 @@
     "/search/issues": {
       "get": {
         "summary": "Search issues and pull requests",
-        "description": "> [!WARNING]\n> **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.\n> You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).",
+        "description": "Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api).\n\nWhen searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted\nsearch results, see [Text match metadata](https://docs.github.com/rest/search/search#text-match-metadata).\n\nFor example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.\n\n`q=windows+label:bug+language:python+state:open&sort=created&order=asc`\n\nThis query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.\n\n> [!NOTE]\n> For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see \"[Searching only issues or pull requests](https://docs.github.com/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests).\"",
         "tags": [
           "search"
         ],
@@ -64420,11 +64420,8 @@
           "githubCloudOnly": false,
           "enabledForGitHubApps": true,
           "category": "search",
-          "subcategory": "search",
-          "deprecationDate": "2025-03-04",
-          "removalDate": "2025-11-04"
-        },
-        "deprecated": true
+          "subcategory": "search"
+        }
       }
     },
     "/search/labels": {
@@ -301311,7 +301308,7 @@
           "created_at": "2022-09-12T12:14:32Z",
           "updated_at": "2022-09-12T12:14:32Z",
           "completed_at": "2022-09-12T13:15:33Z",
-          "status": "completed",
+          "status": "succeeded",
           "actions_workflow_run_id": 3453588,
           "scanned_repositories": [
             {
diff --git a/descriptions-next/api.github.com/api.github.com.2022-11-28.yaml b/descriptions-next/api.github.com/api.github.com.2022-11-28.yaml
index 4249cd2160..599bb3a69e 100644
--- a/descriptions-next/api.github.com/api.github.com.2022-11-28.yaml
+++ b/descriptions-next/api.github.com/api.github.com.2022-11-28.yaml
@@ -46530,9 +46530,19 @@ paths:
     get:
       summary: Search issues and pull requests
       description: |-
-        > [!WARNING]
-        > **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.
-        > You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).
+        Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api).
+
+        When searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted
+        search results, see [Text match metadata](https://docs.github.com/rest/search/search#text-match-metadata).
+
+        For example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.
+
+        `q=windows+label:bug+language:python+state:open&sort=created&order=asc`
+
+        This query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.
+
+        > [!NOTE]
+        > For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see "[Searching only issues or pull requests](https://docs.github.com/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests)."
       tags:
       - search
       operationId: search/issues-and-pull-requests
@@ -46613,9 +46623,6 @@ paths:
         enabledForGitHubApps: true
         category: search
         subcategory: search
-        deprecationDate: '2025-03-04'
-        removalDate: '2025-11-04'
-      deprecated: true
   "/search/labels":
     get:
       summary: Search labels
@@ -223528,7 +223535,7 @@ components:
         created_at: '2022-09-12T12:14:32Z'
         updated_at: '2022-09-12T12:14:32Z'
         completed_at: '2022-09-12T13:15:33Z'
-        status: completed
+        status: succeeded
         actions_workflow_run_id: 3453588
         scanned_repositories:
         - repository:
diff --git a/descriptions-next/api.github.com/api.github.com.json b/descriptions-next/api.github.com/api.github.com.json
index 383f4a8580..d3f91531bc 100644
--- a/descriptions-next/api.github.com/api.github.com.json
+++ b/descriptions-next/api.github.com/api.github.com.json
@@ -64314,7 +64314,7 @@
     "/search/issues": {
       "get": {
         "summary": "Search issues and pull requests",
-        "description": "> [!WARNING]\n> **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.\n> You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).",
+        "description": "Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api).\n\nWhen searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted\nsearch results, see [Text match metadata](https://docs.github.com/rest/search/search#text-match-metadata).\n\nFor example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.\n\n`q=windows+label:bug+language:python+state:open&sort=created&order=asc`\n\nThis query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.\n\n> [!NOTE]\n> For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see \"[Searching only issues or pull requests](https://docs.github.com/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests).\"",
         "tags": [
           "search"
         ],
@@ -64420,11 +64420,8 @@
           "githubCloudOnly": false,
           "enabledForGitHubApps": true,
           "category": "search",
-          "subcategory": "search",
-          "deprecationDate": "2025-03-04",
-          "removalDate": "2025-11-04"
-        },
-        "deprecated": true
+          "subcategory": "search"
+        }
       }
     },
     "/search/labels": {
@@ -301311,7 +301308,7 @@
           "created_at": "2022-09-12T12:14:32Z",
           "updated_at": "2022-09-12T12:14:32Z",
           "completed_at": "2022-09-12T13:15:33Z",
-          "status": "completed",
+          "status": "succeeded",
           "actions_workflow_run_id": 3453588,
           "scanned_repositories": [
             {
diff --git a/descriptions-next/api.github.com/api.github.com.yaml b/descriptions-next/api.github.com/api.github.com.yaml
index 4249cd2160..599bb3a69e 100644
--- a/descriptions-next/api.github.com/api.github.com.yaml
+++ b/descriptions-next/api.github.com/api.github.com.yaml
@@ -46530,9 +46530,19 @@ paths:
     get:
       summary: Search issues and pull requests
       description: |-
-        > [!WARNING]
-        > **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.
-        > You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).
+        Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api).
+
+        When searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted
+        search results, see [Text match metadata](https://docs.github.com/rest/search/search#text-match-metadata).
+
+        For example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.
+
+        `q=windows+label:bug+language:python+state:open&sort=created&order=asc`
+
+        This query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.
+
+        > [!NOTE]
+        > For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see "[Searching only issues or pull requests](https://docs.github.com/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests)."
       tags:
       - search
       operationId: search/issues-and-pull-requests
@@ -46613,9 +46623,6 @@ paths:
         enabledForGitHubApps: true
         category: search
         subcategory: search
-        deprecationDate: '2025-03-04'
-        removalDate: '2025-11-04'
-      deprecated: true
   "/search/labels":
     get:
       summary: Search labels
@@ -223528,7 +223535,7 @@ components:
         created_at: '2022-09-12T12:14:32Z'
         updated_at: '2022-09-12T12:14:32Z'
         completed_at: '2022-09-12T13:15:33Z'
-        status: completed
+        status: succeeded
         actions_workflow_run_id: 3453588
         scanned_repositories:
         - repository:
diff --git a/descriptions-next/api.github.com/dereferenced/api.github.com.2022-11-28.deref.json b/descriptions-next/api.github.com/dereferenced/api.github.com.2022-11-28.deref.json
index d352d001a0..f0563571e1 100644
--- a/descriptions-next/api.github.com/dereferenced/api.github.com.2022-11-28.deref.json
+++ b/descriptions-next/api.github.com/dereferenced/api.github.com.2022-11-28.deref.json
@@ -296745,7 +296745,7 @@
                         "created_at": "2022-09-12T12:14:32Z",
                         "updated_at": "2022-09-12T12:14:32Z",
                         "completed_at": "2022-09-12T13:15:33Z",
-                        "status": "completed",
+                        "status": "succeeded",
                         "actions_workflow_run_id": 3453588,
                         "scanned_repositories": [
                           {
@@ -296928,7 +296928,7 @@
                         "created_at": "2022-09-12T12:14:32Z",
                         "updated_at": "2022-09-12T12:14:32Z",
                         "completed_at": "2022-09-12T13:15:33Z",
-                        "status": "completed",
+                        "status": "succeeded",
                         "actions_workflow_run_id": 3453588,
                         "scanned_repositories": [
                           {
@@ -297111,7 +297111,7 @@
                         "created_at": "2022-09-12T12:14:32Z",
                         "updated_at": "2022-09-12T12:14:32Z",
                         "completed_at": "2022-09-12T13:15:33Z",
-                        "status": "completed",
+                        "status": "succeeded",
                         "actions_workflow_run_id": 3453588,
                         "scanned_repositories": [
                           {
@@ -298578,7 +298578,7 @@
                       "created_at": "2022-09-12T12:14:32Z",
                       "updated_at": "2022-09-12T12:14:32Z",
                       "completed_at": "2022-09-12T13:15:33Z",
-                      "status": "completed",
+                      "status": "succeeded",
                       "actions_workflow_run_id": 3453588,
                       "scanned_repositories": [
                         {
@@ -582110,7 +582110,7 @@
     "/search/issues": {
       "get": {
         "summary": "Search issues and pull requests",
-        "description": "> [!WARNING]\n> **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.\n> You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).",
+        "description": "Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api).\n\nWhen searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted\nsearch results, see [Text match metadata](https://docs.github.com/rest/search/search#text-match-metadata).\n\nFor example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.\n\n`q=windows+label:bug+language:python+state:open&sort=created&order=asc`\n\nThis query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.\n\n> [!NOTE]\n> For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see \"[Searching only issues or pull requests](https://docs.github.com/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests).\"",
         "tags": [
           "search"
         ],
@@ -585185,11 +585185,8 @@
           "githubCloudOnly": false,
           "enabledForGitHubApps": true,
           "category": "search",
-          "subcategory": "search",
-          "deprecationDate": "2025-03-04",
-          "removalDate": "2025-11-04"
-        },
-        "deprecated": true
+          "subcategory": "search"
+        }
       }
     },
     "/search/labels": {
diff --git a/descriptions-next/api.github.com/dereferenced/api.github.com.2022-11-28.deref.yaml b/descriptions-next/api.github.com/dereferenced/api.github.com.2022-11-28.deref.yaml
index d54f2dbb61..3aaab35264 100644
--- a/descriptions-next/api.github.com/dereferenced/api.github.com.2022-11-28.deref.yaml
+++ b/descriptions-next/api.github.com/dereferenced/api.github.com.2022-11-28.deref.yaml
@@ -62759,7 +62759,7 @@ paths:
                       created_at: '2022-09-12T12:14:32Z'
                       updated_at: '2022-09-12T12:14:32Z'
                       completed_at: '2022-09-12T13:15:33Z'
-                      status: completed
+                      status: succeeded
                       actions_workflow_run_id: 3453588
                       scanned_repositories:
                       - repository:
@@ -94899,9 +94899,19 @@ paths:
     get:
       summary: Search issues and pull requests
       description: |-
-        > [!WARNING]
-        > **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.
-        > You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).
+        Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api).
+
+        When searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted
+        search results, see [Text match metadata](https://docs.github.com/rest/search/search#text-match-metadata).
+
+        For example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.
+
+        `q=windows+label:bug+language:python+state:open&sort=created&order=asc`
+
+        This query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.
+
+        > [!NOTE]
+        > For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see "[Searching only issues or pull requests](https://docs.github.com/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests)."
       tags:
       - search
       operationId: search/issues-and-pull-requests
@@ -95250,9 +95260,6 @@ paths:
         enabledForGitHubApps: true
         category: search
         subcategory: search
-        deprecationDate: '2025-03-04'
-        removalDate: '2025-11-04'
-      deprecated: true
   "/search/labels":
     get:
       summary: Search labels
diff --git a/descriptions-next/api.github.com/dereferenced/api.github.com.deref.json b/descriptions-next/api.github.com/dereferenced/api.github.com.deref.json
index d352d001a0..f0563571e1 100644
--- a/descriptions-next/api.github.com/dereferenced/api.github.com.deref.json
+++ b/descriptions-next/api.github.com/dereferenced/api.github.com.deref.json
@@ -296745,7 +296745,7 @@
                         "created_at": "2022-09-12T12:14:32Z",
                         "updated_at": "2022-09-12T12:14:32Z",
                         "completed_at": "2022-09-12T13:15:33Z",
-                        "status": "completed",
+                        "status": "succeeded",
                         "actions_workflow_run_id": 3453588,
                         "scanned_repositories": [
                           {
@@ -296928,7 +296928,7 @@
                         "created_at": "2022-09-12T12:14:32Z",
                         "updated_at": "2022-09-12T12:14:32Z",
                         "completed_at": "2022-09-12T13:15:33Z",
-                        "status": "completed",
+                        "status": "succeeded",
                         "actions_workflow_run_id": 3453588,
                         "scanned_repositories": [
                           {
@@ -297111,7 +297111,7 @@
                         "created_at": "2022-09-12T12:14:32Z",
                         "updated_at": "2022-09-12T12:14:32Z",
                         "completed_at": "2022-09-12T13:15:33Z",
-                        "status": "completed",
+                        "status": "succeeded",
                         "actions_workflow_run_id": 3453588,
                         "scanned_repositories": [
                           {
@@ -298578,7 +298578,7 @@
                       "created_at": "2022-09-12T12:14:32Z",
                       "updated_at": "2022-09-12T12:14:32Z",
                       "completed_at": "2022-09-12T13:15:33Z",
-                      "status": "completed",
+                      "status": "succeeded",
                       "actions_workflow_run_id": 3453588,
                       "scanned_repositories": [
                         {
@@ -582110,7 +582110,7 @@
     "/search/issues": {
       "get": {
         "summary": "Search issues and pull requests",
-        "description": "> [!WARNING]\n> **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.\n> You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).",
+        "description": "Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api).\n\nWhen searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted\nsearch results, see [Text match metadata](https://docs.github.com/rest/search/search#text-match-metadata).\n\nFor example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.\n\n`q=windows+label:bug+language:python+state:open&sort=created&order=asc`\n\nThis query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.\n\n> [!NOTE]\n> For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see \"[Searching only issues or pull requests](https://docs.github.com/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests).\"",
         "tags": [
           "search"
         ],
@@ -585185,11 +585185,8 @@
           "githubCloudOnly": false,
           "enabledForGitHubApps": true,
           "category": "search",
-          "subcategory": "search",
-          "deprecationDate": "2025-03-04",
-          "removalDate": "2025-11-04"
-        },
-        "deprecated": true
+          "subcategory": "search"
+        }
       }
     },
     "/search/labels": {
diff --git a/descriptions-next/api.github.com/dereferenced/api.github.com.deref.yaml b/descriptions-next/api.github.com/dereferenced/api.github.com.deref.yaml
index d54f2dbb61..3aaab35264 100644
--- a/descriptions-next/api.github.com/dereferenced/api.github.com.deref.yaml
+++ b/descriptions-next/api.github.com/dereferenced/api.github.com.deref.yaml
@@ -62759,7 +62759,7 @@ paths:
                       created_at: '2022-09-12T12:14:32Z'
                       updated_at: '2022-09-12T12:14:32Z'
                       completed_at: '2022-09-12T13:15:33Z'
-                      status: completed
+                      status: succeeded
                       actions_workflow_run_id: 3453588
                       scanned_repositories:
                       - repository:
@@ -94899,9 +94899,19 @@ paths:
     get:
       summary: Search issues and pull requests
       description: |-
-        > [!WARNING]
-        > **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.
-        > You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).
+        Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api).
+
+        When searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted
+        search results, see [Text match metadata](https://docs.github.com/rest/search/search#text-match-metadata).
+
+        For example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.
+
+        `q=windows+label:bug+language:python+state:open&sort=created&order=asc`
+
+        This query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.
+
+        > [!NOTE]
+        > For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see "[Searching only issues or pull requests](https://docs.github.com/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests)."
       tags:
       - search
       operationId: search/issues-and-pull-requests
@@ -95250,9 +95260,6 @@ paths:
         enabledForGitHubApps: true
         category: search
         subcategory: search
-        deprecationDate: '2025-03-04'
-        removalDate: '2025-11-04'
-      deprecated: true
   "/search/labels":
     get:
       summary: Search labels
diff --git a/descriptions-next/ghec/dereferenced/ghec.2022-11-28.deref.json b/descriptions-next/ghec/dereferenced/ghec.2022-11-28.deref.json
index fb9355b705..e91e9fb788 100644
--- a/descriptions-next/ghec/dereferenced/ghec.2022-11-28.deref.json
+++ b/descriptions-next/ghec/dereferenced/ghec.2022-11-28.deref.json
@@ -348548,7 +348548,7 @@
                         "created_at": "2022-09-12T12:14:32Z",
                         "updated_at": "2022-09-12T12:14:32Z",
                         "completed_at": "2022-09-12T13:15:33Z",
-                        "status": "completed",
+                        "status": "succeeded",
                         "actions_workflow_run_id": 3453588,
                         "scanned_repositories": [
                           {
@@ -348731,7 +348731,7 @@
                         "created_at": "2022-09-12T12:14:32Z",
                         "updated_at": "2022-09-12T12:14:32Z",
                         "completed_at": "2022-09-12T13:15:33Z",
-                        "status": "completed",
+                        "status": "succeeded",
                         "actions_workflow_run_id": 3453588,
                         "scanned_repositories": [
                           {
@@ -348914,7 +348914,7 @@
                         "created_at": "2022-09-12T12:14:32Z",
                         "updated_at": "2022-09-12T12:14:32Z",
                         "completed_at": "2022-09-12T13:15:33Z",
-                        "status": "completed",
+                        "status": "succeeded",
                         "actions_workflow_run_id": 3453588,
                         "scanned_repositories": [
                           {
@@ -350381,7 +350381,7 @@
                       "created_at": "2022-09-12T12:14:32Z",
                       "updated_at": "2022-09-12T12:14:32Z",
                       "completed_at": "2022-09-12T13:15:33Z",
-                      "status": "completed",
+                      "status": "succeeded",
                       "actions_workflow_run_id": 3453588,
                       "scanned_repositories": [
                         {
@@ -647941,7 +647941,7 @@
     "/search/issues": {
       "get": {
         "summary": "Search issues and pull requests",
-        "description": "> [!WARNING]\n> **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.\n> You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).",
+        "description": "Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/enterprise-cloud@latest//rest/guides/using-pagination-in-the-rest-api).\n\nWhen searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted\nsearch results, see [Text match metadata](https://docs.github.com/enterprise-cloud@latest//rest/search/search#text-match-metadata).\n\nFor example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.\n\n`q=windows+label:bug+language:python+state:open&sort=created&order=asc`\n\nThis query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.\n\n> [!NOTE]\n> For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see \"[Searching only issues or pull requests](https://docs.github.com/enterprise-cloud@latest//github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests).\"",
         "tags": [
           "search"
         ],
@@ -651016,11 +651016,8 @@
           "githubCloudOnly": false,
           "enabledForGitHubApps": true,
           "category": "search",
-          "subcategory": "search",
-          "deprecationDate": "2025-03-04",
-          "removalDate": "2025-11-04"
-        },
-        "deprecated": true
+          "subcategory": "search"
+        }
       }
     },
     "/search/labels": {
diff --git a/descriptions-next/ghec/dereferenced/ghec.2022-11-28.deref.yaml b/descriptions-next/ghec/dereferenced/ghec.2022-11-28.deref.yaml
index ad5c33e3f9..f98220ce86 100644
--- a/descriptions-next/ghec/dereferenced/ghec.2022-11-28.deref.yaml
+++ b/descriptions-next/ghec/dereferenced/ghec.2022-11-28.deref.yaml
@@ -74026,7 +74026,7 @@ paths:
                       created_at: '2022-09-12T12:14:32Z'
                       updated_at: '2022-09-12T12:14:32Z'
                       completed_at: '2022-09-12T13:15:33Z'
-                      status: completed
+                      status: succeeded
                       actions_workflow_run_id: 3453588
                       scanned_repositories:
                       - repository:
@@ -108654,9 +108654,19 @@ paths:
     get:
       summary: Search issues and pull requests
       description: |-
-        > [!WARNING]
-        > **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.
-        > You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).
+        Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/enterprise-cloud@latest//rest/guides/using-pagination-in-the-rest-api).
+
+        When searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted
+        search results, see [Text match metadata](https://docs.github.com/enterprise-cloud@latest//rest/search/search#text-match-metadata).
+
+        For example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.
+
+        `q=windows+label:bug+language:python+state:open&sort=created&order=asc`
+
+        This query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.
+
+        > [!NOTE]
+        > For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see "[Searching only issues or pull requests](https://docs.github.com/enterprise-cloud@latest//github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests)."
       tags:
       - search
       operationId: search/issues-and-pull-requests
@@ -109006,9 +109016,6 @@ paths:
         enabledForGitHubApps: true
         category: search
         subcategory: search
-        deprecationDate: '2025-03-04'
-        removalDate: '2025-11-04'
-      deprecated: true
   "/search/labels":
     get:
       summary: Search labels
diff --git a/descriptions-next/ghec/dereferenced/ghec.deref.json b/descriptions-next/ghec/dereferenced/ghec.deref.json
index fb9355b705..e91e9fb788 100644
--- a/descriptions-next/ghec/dereferenced/ghec.deref.json
+++ b/descriptions-next/ghec/dereferenced/ghec.deref.json
@@ -348548,7 +348548,7 @@
                         "created_at": "2022-09-12T12:14:32Z",
                         "updated_at": "2022-09-12T12:14:32Z",
                         "completed_at": "2022-09-12T13:15:33Z",
-                        "status": "completed",
+                        "status": "succeeded",
                         "actions_workflow_run_id": 3453588,
                         "scanned_repositories": [
                           {
@@ -348731,7 +348731,7 @@
                         "created_at": "2022-09-12T12:14:32Z",
                         "updated_at": "2022-09-12T12:14:32Z",
                         "completed_at": "2022-09-12T13:15:33Z",
-                        "status": "completed",
+                        "status": "succeeded",
                         "actions_workflow_run_id": 3453588,
                         "scanned_repositories": [
                           {
@@ -348914,7 +348914,7 @@
                         "created_at": "2022-09-12T12:14:32Z",
                         "updated_at": "2022-09-12T12:14:32Z",
                         "completed_at": "2022-09-12T13:15:33Z",
-                        "status": "completed",
+                        "status": "succeeded",
                         "actions_workflow_run_id": 3453588,
                         "scanned_repositories": [
                           {
@@ -350381,7 +350381,7 @@
                       "created_at": "2022-09-12T12:14:32Z",
                       "updated_at": "2022-09-12T12:14:32Z",
                       "completed_at": "2022-09-12T13:15:33Z",
-                      "status": "completed",
+                      "status": "succeeded",
                       "actions_workflow_run_id": 3453588,
                       "scanned_repositories": [
                         {
@@ -647941,7 +647941,7 @@
     "/search/issues": {
       "get": {
         "summary": "Search issues and pull requests",
-        "description": "> [!WARNING]\n> **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.\n> You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).",
+        "description": "Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/enterprise-cloud@latest//rest/guides/using-pagination-in-the-rest-api).\n\nWhen searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted\nsearch results, see [Text match metadata](https://docs.github.com/enterprise-cloud@latest//rest/search/search#text-match-metadata).\n\nFor example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.\n\n`q=windows+label:bug+language:python+state:open&sort=created&order=asc`\n\nThis query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.\n\n> [!NOTE]\n> For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see \"[Searching only issues or pull requests](https://docs.github.com/enterprise-cloud@latest//github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests).\"",
         "tags": [
           "search"
         ],
@@ -651016,11 +651016,8 @@
           "githubCloudOnly": false,
           "enabledForGitHubApps": true,
           "category": "search",
-          "subcategory": "search",
-          "deprecationDate": "2025-03-04",
-          "removalDate": "2025-11-04"
-        },
-        "deprecated": true
+          "subcategory": "search"
+        }
       }
     },
     "/search/labels": {
diff --git a/descriptions-next/ghec/dereferenced/ghec.deref.yaml b/descriptions-next/ghec/dereferenced/ghec.deref.yaml
index ad5c33e3f9..f98220ce86 100644
--- a/descriptions-next/ghec/dereferenced/ghec.deref.yaml
+++ b/descriptions-next/ghec/dereferenced/ghec.deref.yaml
@@ -74026,7 +74026,7 @@ paths:
                       created_at: '2022-09-12T12:14:32Z'
                       updated_at: '2022-09-12T12:14:32Z'
                       completed_at: '2022-09-12T13:15:33Z'
-                      status: completed
+                      status: succeeded
                       actions_workflow_run_id: 3453588
                       scanned_repositories:
                       - repository:
@@ -108654,9 +108654,19 @@ paths:
     get:
       summary: Search issues and pull requests
       description: |-
-        > [!WARNING]
-        > **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.
-        > You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).
+        Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/enterprise-cloud@latest//rest/guides/using-pagination-in-the-rest-api).
+
+        When searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted
+        search results, see [Text match metadata](https://docs.github.com/enterprise-cloud@latest//rest/search/search#text-match-metadata).
+
+        For example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.
+
+        `q=windows+label:bug+language:python+state:open&sort=created&order=asc`
+
+        This query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.
+
+        > [!NOTE]
+        > For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see "[Searching only issues or pull requests](https://docs.github.com/enterprise-cloud@latest//github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests)."
       tags:
       - search
       operationId: search/issues-and-pull-requests
@@ -109006,9 +109016,6 @@ paths:
         enabledForGitHubApps: true
         category: search
         subcategory: search
-        deprecationDate: '2025-03-04'
-        removalDate: '2025-11-04'
-      deprecated: true
   "/search/labels":
     get:
       summary: Search labels
diff --git a/descriptions-next/ghec/ghec.2022-11-28.json b/descriptions-next/ghec/ghec.2022-11-28.json
index 0e072f9694..ff64463c3d 100644
--- a/descriptions-next/ghec/ghec.2022-11-28.json
+++ b/descriptions-next/ghec/ghec.2022-11-28.json
@@ -77821,7 +77821,7 @@
     "/search/issues": {
       "get": {
         "summary": "Search issues and pull requests",
-        "description": "> [!WARNING]\n> **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.\n> You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).",
+        "description": "Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/enterprise-cloud@latest//rest/guides/using-pagination-in-the-rest-api).\n\nWhen searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted\nsearch results, see [Text match metadata](https://docs.github.com/enterprise-cloud@latest//rest/search/search#text-match-metadata).\n\nFor example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.\n\n`q=windows+label:bug+language:python+state:open&sort=created&order=asc`\n\nThis query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.\n\n> [!NOTE]\n> For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see \"[Searching only issues or pull requests](https://docs.github.com/enterprise-cloud@latest//github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests).\"",
         "tags": [
           "search"
         ],
@@ -77927,11 +77927,8 @@
           "githubCloudOnly": false,
           "enabledForGitHubApps": true,
           "category": "search",
-          "subcategory": "search",
-          "deprecationDate": "2025-03-04",
-          "removalDate": "2025-11-04"
-        },
-        "deprecated": true
+          "subcategory": "search"
+        }
       }
     },
     "/search/labels": {
@@ -322999,7 +322996,7 @@
           "created_at": "2022-09-12T12:14:32Z",
           "updated_at": "2022-09-12T12:14:32Z",
           "completed_at": "2022-09-12T13:15:33Z",
-          "status": "completed",
+          "status": "succeeded",
           "actions_workflow_run_id": 3453588,
           "scanned_repositories": [
             {
diff --git a/descriptions-next/ghec/ghec.2022-11-28.yaml b/descriptions-next/ghec/ghec.2022-11-28.yaml
index 15ee634646..268b7aff88 100644
--- a/descriptions-next/ghec/ghec.2022-11-28.yaml
+++ b/descriptions-next/ghec/ghec.2022-11-28.yaml
@@ -56072,9 +56072,19 @@ paths:
     get:
       summary: Search issues and pull requests
       description: |-
-        > [!WARNING]
-        > **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.
-        > You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).
+        Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/enterprise-cloud@latest//rest/guides/using-pagination-in-the-rest-api).
+
+        When searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted
+        search results, see [Text match metadata](https://docs.github.com/enterprise-cloud@latest//rest/search/search#text-match-metadata).
+
+        For example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.
+
+        `q=windows+label:bug+language:python+state:open&sort=created&order=asc`
+
+        This query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.
+
+        > [!NOTE]
+        > For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see "[Searching only issues or pull requests](https://docs.github.com/enterprise-cloud@latest//github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests)."
       tags:
       - search
       operationId: search/issues-and-pull-requests
@@ -56156,9 +56166,6 @@ paths:
         enabledForGitHubApps: true
         category: search
         subcategory: search
-        deprecationDate: '2025-03-04'
-        removalDate: '2025-11-04'
-      deprecated: true
   "/search/labels":
     get:
       summary: Search labels
@@ -239035,7 +239042,7 @@ components:
         created_at: '2022-09-12T12:14:32Z'
         updated_at: '2022-09-12T12:14:32Z'
         completed_at: '2022-09-12T13:15:33Z'
-        status: completed
+        status: succeeded
         actions_workflow_run_id: 3453588
         scanned_repositories:
         - repository:
diff --git a/descriptions-next/ghec/ghec.json b/descriptions-next/ghec/ghec.json
index 0e072f9694..ff64463c3d 100644
--- a/descriptions-next/ghec/ghec.json
+++ b/descriptions-next/ghec/ghec.json
@@ -77821,7 +77821,7 @@
     "/search/issues": {
       "get": {
         "summary": "Search issues and pull requests",
-        "description": "> [!WARNING]\n> **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.\n> You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).",
+        "description": "Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/enterprise-cloud@latest//rest/guides/using-pagination-in-the-rest-api).\n\nWhen searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted\nsearch results, see [Text match metadata](https://docs.github.com/enterprise-cloud@latest//rest/search/search#text-match-metadata).\n\nFor example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.\n\n`q=windows+label:bug+language:python+state:open&sort=created&order=asc`\n\nThis query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.\n\n> [!NOTE]\n> For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see \"[Searching only issues or pull requests](https://docs.github.com/enterprise-cloud@latest//github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests).\"",
         "tags": [
           "search"
         ],
@@ -77927,11 +77927,8 @@
           "githubCloudOnly": false,
           "enabledForGitHubApps": true,
           "category": "search",
-          "subcategory": "search",
-          "deprecationDate": "2025-03-04",
-          "removalDate": "2025-11-04"
-        },
-        "deprecated": true
+          "subcategory": "search"
+        }
       }
     },
     "/search/labels": {
@@ -322999,7 +322996,7 @@
           "created_at": "2022-09-12T12:14:32Z",
           "updated_at": "2022-09-12T12:14:32Z",
           "completed_at": "2022-09-12T13:15:33Z",
-          "status": "completed",
+          "status": "succeeded",
           "actions_workflow_run_id": 3453588,
           "scanned_repositories": [
             {
diff --git a/descriptions-next/ghec/ghec.yaml b/descriptions-next/ghec/ghec.yaml
index 15ee634646..268b7aff88 100644
--- a/descriptions-next/ghec/ghec.yaml
+++ b/descriptions-next/ghec/ghec.yaml
@@ -56072,9 +56072,19 @@ paths:
     get:
       summary: Search issues and pull requests
       description: |-
-        > [!WARNING]
-        > **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.
-        > You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).
+        Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/enterprise-cloud@latest//rest/guides/using-pagination-in-the-rest-api).
+
+        When searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted
+        search results, see [Text match metadata](https://docs.github.com/enterprise-cloud@latest//rest/search/search#text-match-metadata).
+
+        For example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.
+
+        `q=windows+label:bug+language:python+state:open&sort=created&order=asc`
+
+        This query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.
+
+        > [!NOTE]
+        > For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see "[Searching only issues or pull requests](https://docs.github.com/enterprise-cloud@latest//github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests)."
       tags:
       - search
       operationId: search/issues-and-pull-requests
@@ -56156,9 +56166,6 @@ paths:
         enabledForGitHubApps: true
         category: search
         subcategory: search
-        deprecationDate: '2025-03-04'
-        removalDate: '2025-11-04'
-      deprecated: true
   "/search/labels":
     get:
       summary: Search labels
@@ -239035,7 +239042,7 @@ components:
         created_at: '2022-09-12T12:14:32Z'
         updated_at: '2022-09-12T12:14:32Z'
         completed_at: '2022-09-12T13:15:33Z'
-        status: completed
+        status: succeeded
         actions_workflow_run_id: 3453588
         scanned_repositories:
         - repository:
diff --git a/descriptions-next/ghes-3.17/dereferenced/ghes-3.17.2022-11-28.deref.json b/descriptions-next/ghes-3.17/dereferenced/ghes-3.17.2022-11-28.deref.json
index 71a5130184..0ef031c2cc 100644
--- a/descriptions-next/ghes-3.17/dereferenced/ghes-3.17.2022-11-28.deref.json
+++ b/descriptions-next/ghes-3.17/dereferenced/ghes-3.17.2022-11-28.deref.json
@@ -492520,7 +492520,7 @@
     "/search/issues": {
       "get": {
         "summary": "Search issues and pull requests",
-        "description": "> [!WARNING]\n> **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.\n> You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).",
+        "description": "Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.17/rest/guides/using-pagination-in-the-rest-api).\n\nWhen searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted\nsearch results, see [Text match metadata](https://docs.github.com/enterprise-server@3.17/rest/search/search#text-match-metadata).\n\nFor example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.\n\n`q=windows+label:bug+language:python+state:open&sort=created&order=asc`\n\nThis query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.\n\n> [!NOTE]\n> For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see \"[Searching only issues or pull requests](https://docs.github.com/enterprise-server@3.17/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests).\"",
         "tags": [
           "search"
         ],
@@ -495595,11 +495595,8 @@
           "githubCloudOnly": false,
           "enabledForGitHubApps": true,
           "category": "search",
-          "subcategory": "search",
-          "deprecationDate": "2025-03-04",
-          "removalDate": "2025-11-04"
-        },
-        "deprecated": true
+          "subcategory": "search"
+        }
       }
     },
     "/search/labels": {
diff --git a/descriptions-next/ghes-3.17/dereferenced/ghes-3.17.2022-11-28.deref.yaml b/descriptions-next/ghes-3.17/dereferenced/ghes-3.17.2022-11-28.deref.yaml
index 33a2343a66..6588d553ae 100644
--- a/descriptions-next/ghes-3.17/dereferenced/ghes-3.17.2022-11-28.deref.yaml
+++ b/descriptions-next/ghes-3.17/dereferenced/ghes-3.17.2022-11-28.deref.yaml
@@ -87367,9 +87367,19 @@ paths:
     get:
       summary: Search issues and pull requests
       description: |-
-        > [!WARNING]
-        > **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.
-        > You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).
+        Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.17/rest/guides/using-pagination-in-the-rest-api).
+
+        When searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted
+        search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.17/rest/search/search#text-match-metadata).
+
+        For example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.
+
+        `q=windows+label:bug+language:python+state:open&sort=created&order=asc`
+
+        This query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.
+
+        > [!NOTE]
+        > For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see "[Searching only issues or pull requests](https://docs.github.com/enterprise-server@3.17/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests)."
       tags:
       - search
       operationId: search/issues-and-pull-requests
@@ -87719,9 +87729,6 @@ paths:
         enabledForGitHubApps: true
         category: search
         subcategory: search
-        deprecationDate: '2025-03-04'
-        removalDate: '2025-11-04'
-      deprecated: true
   "/search/labels":
     get:
       summary: Search labels
diff --git a/descriptions-next/ghes-3.17/dereferenced/ghes-3.17.deref.json b/descriptions-next/ghes-3.17/dereferenced/ghes-3.17.deref.json
index 71a5130184..0ef031c2cc 100644
--- a/descriptions-next/ghes-3.17/dereferenced/ghes-3.17.deref.json
+++ b/descriptions-next/ghes-3.17/dereferenced/ghes-3.17.deref.json
@@ -492520,7 +492520,7 @@
     "/search/issues": {
       "get": {
         "summary": "Search issues and pull requests",
-        "description": "> [!WARNING]\n> **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.\n> You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).",
+        "description": "Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.17/rest/guides/using-pagination-in-the-rest-api).\n\nWhen searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted\nsearch results, see [Text match metadata](https://docs.github.com/enterprise-server@3.17/rest/search/search#text-match-metadata).\n\nFor example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.\n\n`q=windows+label:bug+language:python+state:open&sort=created&order=asc`\n\nThis query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.\n\n> [!NOTE]\n> For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see \"[Searching only issues or pull requests](https://docs.github.com/enterprise-server@3.17/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests).\"",
         "tags": [
           "search"
         ],
@@ -495595,11 +495595,8 @@
           "githubCloudOnly": false,
           "enabledForGitHubApps": true,
           "category": "search",
-          "subcategory": "search",
-          "deprecationDate": "2025-03-04",
-          "removalDate": "2025-11-04"
-        },
-        "deprecated": true
+          "subcategory": "search"
+        }
       }
     },
     "/search/labels": {
diff --git a/descriptions-next/ghes-3.17/dereferenced/ghes-3.17.deref.yaml b/descriptions-next/ghes-3.17/dereferenced/ghes-3.17.deref.yaml
index 33a2343a66..6588d553ae 100644
--- a/descriptions-next/ghes-3.17/dereferenced/ghes-3.17.deref.yaml
+++ b/descriptions-next/ghes-3.17/dereferenced/ghes-3.17.deref.yaml
@@ -87367,9 +87367,19 @@ paths:
     get:
       summary: Search issues and pull requests
       description: |-
-        > [!WARNING]
-        > **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.
-        > You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).
+        Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.17/rest/guides/using-pagination-in-the-rest-api).
+
+        When searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted
+        search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.17/rest/search/search#text-match-metadata).
+
+        For example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.
+
+        `q=windows+label:bug+language:python+state:open&sort=created&order=asc`
+
+        This query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.
+
+        > [!NOTE]
+        > For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see "[Searching only issues or pull requests](https://docs.github.com/enterprise-server@3.17/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests)."
       tags:
       - search
       operationId: search/issues-and-pull-requests
@@ -87719,9 +87729,6 @@ paths:
         enabledForGitHubApps: true
         category: search
         subcategory: search
-        deprecationDate: '2025-03-04'
-        removalDate: '2025-11-04'
-      deprecated: true
   "/search/labels":
     get:
       summary: Search labels
diff --git a/descriptions-next/ghes-3.17/ghes-3.17.2022-11-28.json b/descriptions-next/ghes-3.17/ghes-3.17.2022-11-28.json
index 9690e01b0c..1f7bfce991 100644
--- a/descriptions-next/ghes-3.17/ghes-3.17.2022-11-28.json
+++ b/descriptions-next/ghes-3.17/ghes-3.17.2022-11-28.json
@@ -60180,7 +60180,7 @@
     "/search/issues": {
       "get": {
         "summary": "Search issues and pull requests",
-        "description": "> [!WARNING]\n> **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.\n> You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).",
+        "description": "Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.17/rest/guides/using-pagination-in-the-rest-api).\n\nWhen searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted\nsearch results, see [Text match metadata](https://docs.github.com/enterprise-server@3.17/rest/search/search#text-match-metadata).\n\nFor example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.\n\n`q=windows+label:bug+language:python+state:open&sort=created&order=asc`\n\nThis query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.\n\n> [!NOTE]\n> For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see \"[Searching only issues or pull requests](https://docs.github.com/enterprise-server@3.17/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests).\"",
         "tags": [
           "search"
         ],
@@ -60286,11 +60286,8 @@
           "githubCloudOnly": false,
           "enabledForGitHubApps": true,
           "category": "search",
-          "subcategory": "search",
-          "deprecationDate": "2025-03-04",
-          "removalDate": "2025-11-04"
-        },
-        "deprecated": true
+          "subcategory": "search"
+        }
       }
     },
     "/search/labels": {
diff --git a/descriptions-next/ghes-3.17/ghes-3.17.2022-11-28.yaml b/descriptions-next/ghes-3.17/ghes-3.17.2022-11-28.yaml
index 1abee29d8f..fa72d39a6f 100644
--- a/descriptions-next/ghes-3.17/ghes-3.17.2022-11-28.yaml
+++ b/descriptions-next/ghes-3.17/ghes-3.17.2022-11-28.yaml
@@ -43568,9 +43568,19 @@ paths:
     get:
       summary: Search issues and pull requests
       description: |-
-        > [!WARNING]
-        > **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.
-        > You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).
+        Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.17/rest/guides/using-pagination-in-the-rest-api).
+
+        When searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted
+        search results, see [Text match metadata](https://docs.github.com/enterprise-server@3.17/rest/search/search#text-match-metadata).
+
+        For example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.
+
+        `q=windows+label:bug+language:python+state:open&sort=created&order=asc`
+
+        This query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.
+
+        > [!NOTE]
+        > For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see "[Searching only issues or pull requests](https://docs.github.com/enterprise-server@3.17/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests)."
       tags:
       - search
       operationId: search/issues-and-pull-requests
@@ -43652,9 +43662,6 @@ paths:
         enabledForGitHubApps: true
         category: search
         subcategory: search
-        deprecationDate: '2025-03-04'
-        removalDate: '2025-11-04'
-      deprecated: true
   "/search/labels":
     get:
       summary: Search labels
diff --git a/descriptions-next/ghes-3.17/ghes-3.17.json b/descriptions-next/ghes-3.17/ghes-3.17.json
index 9690e01b0c..1f7bfce991 100644
--- a/descriptions-next/ghes-3.17/ghes-3.17.json
+++ b/descriptions-next/ghes-3.17/ghes-3.17.json
@@ -60180,7 +60180,7 @@
     "/search/issues": {
       "get": {
         "summary": "Search issues and pull requests",
-        "description": "> [!WARNING]\n> **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.\n> You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).",
+        "description": "Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/enterprise-server@3.17/rest/guides/using-pagination-in-the-rest-api).\n\nWhen searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted\nsearch results, see [Text match metadata](https://docs.github.com/enterprise-server@3.17/rest/search/search#text-match-metadata).\n\nFor example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.\n\n`q=windows+label:bug+language:python+state:open&sort=created&order=asc`\n\nThis query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.\n\n> [!NOTE]\n> For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see \"[Searching only issues or pull requests](https://docs.github.com/enterprise-server@3.17/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests).\"",
         "tags": [
           "search"
         ],
@@ -60286,11 +60286,8 @@
           "githubCloudOnly": false,
           "enabledForGitHubApps": true,
           "category": "search",
-          "subcategory": "search",
-          "deprecationDate": "2025-03-04",
-          "removalDate": "2025-11-04"
-        },
-        "deprecated": true
+          "subcategory": "search"
+        }
       }
     },
     "/search/labels": {
diff --git a/descriptions-next/ghes-3.17/ghes-3.17.yaml b/descriptions-next/ghes-3.17/ghes-3.17.yaml
index 1abee29d8f..fa72d39a6f 100644
--- a/descriptions-next/ghes-3.17/ghes-3.17.yaml
+++ b/descriptions-next/ghes-3.17/ghes-3.17.yaml
@@ -43568,9 +43568,19 @@ paths:
     get:
       summary: Search issues and pull requests
       description: |-
-        > [!WARNING]
-        > **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.
-        > You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).
+        Find issues by st{"code":"internal","msg":"git-diff-tree: context deadline exceeded","meta":{"cause":"*fmt.wrapError"}}