1
0
mirror of synced 2025-12-19 09:57:42 -05:00

Enable GitHub Enterprise Server 3.13 release candidate on GitHub Docs (#50165)

Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com>
Co-authored-by: Steve Guntrip <stevecat@github.com>
Co-authored-by: Felicity Chapman <felicitymay@github.com>
Co-authored-by: isaacmbrown <isaacmbrown@github.com>
Co-authored-by: docs-bot <77750099+docs-bot@users.noreply.github.com>
Co-authored-by: Peter Bengtsson <peterbe@github.com>
Co-authored-by: Pallavi <96553709+pallsama@users.noreply.github.com>
This commit is contained in:
Rachael Rose Renk
2024-05-16 08:26:02 -06:00
committed by GitHub
parent c6e1ceff03
commit 4fc4e97dc0
61 changed files with 901349 additions and 57 deletions

View File

@@ -52,6 +52,7 @@ If you run analysis in an external CI system, we recommend using the same versio
| {% data variables.product.product_name %} version | Recommended {% data variables.product.prodname_codeql_cli %} version |
| ------------------------------------------------- | ---------------------- |
| 3.13 | 2.16.6 ([changelog](https://codeql.github.com/docs/codeql-overview/codeql-changelog/codeql-cli-2.16.6/)) |
| 3.12 | 2.15.5 ([changelog](https://codeql.github.com/docs/codeql-overview/codeql-changelog/codeql-cli-2.15.5/)) |
| 3.11 | 2.14.6 ([changelog](https://codeql.github.com/docs/codeql-overview/codeql-changelog/codeql-cli-2.14.6/)) |
| 3.10 | 2.13.5 ([changelog](https://codeql.github.com/docs/codeql-overview/codeql-changelog/codeql-cli-2.13.5/)) |
@@ -66,6 +67,7 @@ For instances with {% data variables.product.prodname_actions %} enabled, self-h
| {% data variables.product.product_name %} version | Minimum Runner version |
| ------------------------------------------------- | ---------------------- |
| 3.13 | 2.314.1 ([release notes](https://github.com/actions/runner/releases/tag/v2.314.1)) |
| 3.12 | 2.311.0 ([release notes](https://github.com/actions/runner/releases/tag/v2.311.0)) |
| 3.11 | 2.309.0 ([release notes](https://github.com/actions/runner/releases/tag/v2.309.0)) |
| 3.10 | 2.304.0 ([release notes](https://github.com/actions/runner/releases/tag/v2.304.0)) |

View File

@@ -67,6 +67,13 @@ Use an upgrade package to upgrade a {% data variables.product.prodname_ghe_serve
### Upgrading the cluster nodes
1. Enable maintenance mode according to your scheduled window by connecting to the administrative shell of any cluster node and running `ghe-cluster-maintenance -s`.
{% ifversion ghes > 3.10 and ghes < 3.15 %}
1. If you're upgrading from version 3.11 or 3.12 to version 3.13 or later, Elasticsearch will be upgraded as part of the upgrade to your cluster. For more information, see "[AUTOTITLE](/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/preparing-for-the-elasticsearch-upgrade)."
Before upgrading, you will need to run a script to prepare your cluster for an upgrade to 3.13 or 3.14.
1. Ensure you are running the required patch release for your current version: **3.11.9** or later for 3.11, or **3.12.3** or later for 3.12.
1. On any `elasticsearch-server` node, run `/usr/local/share/enterprise/ghe-es-auditlog-cluster-rebalance`.
{% endif %}
1. **With the exception of the primary MySQL node**, connect to the administrative shell of each of the {% data variables.product.prodname_ghe_server %} nodes.
Run the `ghe-upgrade` command, providing the package file name you downloaded in Step 4 of [Preparing to upgrade](#preparing-to-upgrade):

View File

@@ -18,6 +18,7 @@ children:
- /increasing-storage-capacity
- /increasing-cpu-or-memory-resources
- /migrating-from-github-enterprise-1110x-to-2123
- /preparing-for-the-elasticsearch-upgrade
- /known-issues-with-upgrades-to-your-instance
shortTitle: Update VM & resources
---

View File

@@ -0,0 +1,54 @@
---
title: Preparing for the Elasticsearch upgrade in {% data variables.product.prodname_ghe_server %} 3.13
intro: 'As part of upgrading {% data variables.product.prodname_ghe_server %} to version 3.13 or later, the Elasticsearch service will be upgraded.'
versions:
ghes: '>3.10 <3.15'
type: reference
topics:
- Enterprise
- Upgrades
shortTitle: Elasticsearch upgrade in 3.13
allowTitleToDifferFromFilename: true
---
## Overview
Elasticsearch (ES) powers the search functionality on your {% data variables.product.prodname_ghe_server %} instance. To bring the benefits of better performance and security posture, when you upgrade your instance to version 3.13 or later, the Elasticsearch version in the appliance will be upgraded from 5.6.16 to 8.7.0.
The following sections help administrators prepare for and monitor the Elasticsearch upgrade. The key points are:
- The upgrade will temporarily degrade the experience of the search and audit log features.
- If you're upgrading an instance in a cluster configuration, you must run a script to prepare your cluster for the ES upgrade. See "[AUTOTITLE](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/upgrading-a-cluster#upgrading-the-cluster-nodes)."
- For backups, all customers should take a snapshot of their instance when the upgrade is complete.
## Impact on search and audit logs
All search indexes will be rebuilt after the upgrade to ES8. Users will experience degraded search experience during the rebuild, but the instance is otherwise expected to be functional and available. The index rebuild process depends on the size of the data set and may take a few hours to days.
Audit logs will not be available immediately after upgrade, and it may take several hours to migrate all audit logs.
We strongly recommend you take a backup (using backup-utils) immediately following completion of the index rebuild and use that snapshot for all future restores. See "[AUTOTITLE](/admin/backing-up-and-restoring-your-instance/configuring-backups-on-your-instance)." If you restore a backup from an instance running {% data variables.product.prodname_ghe_server %} 3.11 or 3.12, then any content that relies on ES will only be available after the ES indexes have been migrated and rebuilt on the 3.13 instance.
## Monitoring the Elasticsearch upgrade
You can monitor the progress of the ES upgrade in the site admin dashboard.
1. In the upper-right corner of any page, click {% octicon "rocket" aria-label="Site admin" %}.
1. In the left sidebar, click **Search indexes**.
When the index rebuild is complete, all the search indexes should show green and "100%."
## Changing the number of repair workers
By default, the number of index repair workers is set to the number of CPU cores divided by 8 (with an upper bound of 8). To speed up the index rebuild, you can adjust the worker count. However, before doing so, you should consider the potential impact to the load.
{% data reusables.enterprise_installation.ssh-into-instance %}
1. To change the number of workers, enter the following command.
```shell copy
ghe-config app.github.es-workers NUMBER-OF-WORKERS
```
1. Run `ghe-config-apply`.
You can also adjust the worker count for individual index rebuilds in the "Search Indexes" section of the site admin dashboard. See the "[Monitoring the Elasticsearch upgrade](#monitoring-the-elasticsearch-upgrade)" section.

View File

@@ -85,7 +85,7 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr
|<kbd>a</kbd> | Show or hide annotations on diffs
|<kbd>b</kbd> | Open blame view. For more information, see "[AUTOTITLE](/repositories/working-with-files/using-files/viewing-a-file)."
{% ifversion code-search-code-view %}
{% ifversion code-view-ui %}
## Navigating within code files
@@ -95,7 +95,10 @@ If you view a code file in a repository using the **Code** view and click on any
|-----------|------------
|<kbd>Shift</kbd>+<kbd>J</kbd>| Highlights the line that is currently selected by the cursor within the code file
|<kbd>Shift</kbd>+<kbd>Option</kbd>+<kbd>C</kbd> (Mac) or </br> <kbd>Shift</kbd>+<kbd>Alt</kbd>+<kbd>C</kbd> (Windows/Linux) | If a line of code is currently selected, this shortcut opens the line menu for that line, appearing under {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} to the left of the line
| {% ifversion code-search-upgrade %} |
|<kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) or </br> <kbd>Control</kbd>+<kbd>Enter</kbd> (Windows/Linux) | Highlights the code symbol currently selected by the cursor and all other occurrences of the symbol in the code, and shows the symbol in the symbols pane
| {% endif %} |
{% endif %}
## Comments

View File

@@ -15,7 +15,7 @@ redirect_from:
## About supported languages
Most {% data variables.product.prodname_dotcom %} features work regardless of which languages your code is written in. You can search for code or enable syntax highlighting based on any language known to {% data variables.product.prodname_dotcom %}. For more information, see "[AUTOTITLE]{% ifversion code-search-code-view %}(/search-github/github-code-search/understanding-github-code-search-syntax#language-qualifier){% else %}(/search-github/searching-on-github/searching-code#search-by-language){% endif %}" or "[AUTOTITLE](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks#syntax-highlighting)."
Most {% data variables.product.prodname_dotcom %} features work regardless of which languages your code is written in. You can search for code or enable syntax highlighting based on any language known to {% data variables.product.prodname_dotcom %}. For more information, see "[AUTOTITLE]{% ifversion code-search-upgrade %}(/search-github/github-code-search/understanding-github-code-search-syntax#language-qualifier){% else %}(/search-github/searching-on-github/searching-code#search-by-language){% endif %}" or "[AUTOTITLE](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks#syntax-highlighting)."
Some {% data variables.product.prodname_dotcom %} products have features that are currently only supported for a subset of programming languages.

View File

@@ -96,7 +96,7 @@ You can make and save changes to the files in your repository. On {% data variab
1. Under the `readme-edits` branch you created, click the `README.md` file.
1. To edit the file, click {% octicon "pencil" aria-label="Edit file" %}.
1. In the editor, write a bit about yourself.
{% ifversion code-search-code-view %}1. Click **Commit changes...**.{% endif %}
{% ifversion code-view-ui %}1. Click **Commit changes...**.{% endif %}
1. In the "Commit changes" box, write a commit message that describes your changes.
1. Click **Commit changes**.

View File

@@ -28,7 +28,7 @@ Custom property names and values may only contain certain characters:
You can add custom properties to your organization and set values for those properties for repositories in your organization.
You can also use the REST API to create and manage custom properties for an organization. For more information, see "[AUTOTITLE](/rest/orgs/custom-properties)."
{% ifversion ghec %}You can also use the REST API to create and manage custom properties for an organization. For more information, see "[AUTOTITLE](/rest/orgs/custom-properties)."{% endif %}
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
@@ -60,7 +60,7 @@ You can set values for custom properties for repositories in your organization.
People with read permissions to a repository can view the values of custom properties for that repository, but they can't edit those values.
You can also use the REST API to list the custom properties assigned to a repository by your organization. For more information, see "[AUTOTITLE](/rest/repos/custom-properties)."
{% ifversion ghec %}You can also use the REST API to list the custom properties assigned to a repository by your organization. For more information, see "[AUTOTITLE](/rest/repos/custom-properties)."{% endif %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}

View File

@@ -44,7 +44,7 @@ You can create a branch in different ways on {% data variables.product.product_n
### Creating a branch using the branch dropdown
{% data reusables.repositories.navigate-to-repo %}
{% ifversion code-search-code-view %}
{% ifversion code-view-ui %}
1. Select the {% octicon "git-branch" aria-hidden="true" %} branch dropdown menu, in the file tree view or at the top of the integrated file editor.
![Screenshot of the file tree view for a repository. A dropdown menu for branches is outlined in dark orange.](/assets/images/help/branches/file-tree-view-branch-dropdown.png)

View File

@@ -28,7 +28,7 @@ When creating a file on {% data variables.product.product_name %}, consider the
1. In the file name field, type the name and extension for the file. To create subdirectories, type the `/` directory separator.
1. In the file contents text box, type content for the file.
1. To review the new content, above the file contents, click **Preview**.
{% ifversion code-search-code-view %}
{% ifversion code-view-ui %}
![Screenshot of a file in edit mode. Above the text box for editing file contents, a tab, labeled "Preview", outlined in dark orange.](/assets/images/help/repository/new-file-preview.png)
{% else %}
![Screenshot of a file in edit mode. Above the text box for editing file contents, a tab, labeled "Preview", outlined in dark orange.](/assets/images/enterprise/repository/new-file-preview.png)

View File

@@ -27,7 +27,7 @@ If the file or directory you deleted contains sensitive data, the data will stil
## Deleting a file
1. Browse to the file in your repository that you want to delete.
{% ifversion code-search-code-view %}
{% ifversion code-view-ui %}
1. In the top-right corner, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} dropdown menu, then click **Delete file**.
![Screenshot of the file list for a directory. To the right of the directory name, a button, labeled with a kebab icon, is outlined in dark orange.](/assets/images/help/repository/delete-file-button.png)

View File

@@ -49,9 +49,9 @@ To learn more about these approaches, see "[Precise and search-based navigation]
Future releases will add _precise code navigation_ for more languages, which is a code navigation approach that can give more accurate results.
{% ifversion code-search-code-view %}You can use keyboard shortcuts to navigate within a code file. For more information, see "[AUTOTITLE](/get-started/accessibility/keyboard-shortcuts#navigating-within-code-files)."{% endif %}
{% ifversion code-view-ui %}You can use keyboard shortcuts to navigate within a code file. For more information, see "[AUTOTITLE](/get-started/accessibility/keyboard-shortcuts#navigating-within-code-files)."{% endif %}
{% ifversion code-search-code-view %}
{% ifversion code-search-upgrade %}
## Using the symbols pane
@@ -109,4 +109,4 @@ If code navigation is enabled for you but you don't see links to the definitions
## Further reading
- "[AUTOTITLE]{% ifversion code-search-code-view %}(/search-github/github-code-search/about-github-code-search){% else %}(/search-github/searching-on-github/searching-code){% endif %}"
- "[AUTOTITLE]{% ifversion code-search-upgrade %}(/search-github/github-code-search/about-github-code-search){% else %}(/search-github/searching-on-github/searching-code){% endif %}"

View File

@@ -23,14 +23,14 @@ With the raw view, you can view or copy the raw content of a file without any st
{% data reusables.repositories.navigate-to-repo %}
1. Click the file that you want to view.
1. In the upper-right corner of the file view, click **Raw**.
{% ifversion code-search-code-view %}
{% ifversion code-view-ui %}
![Screenshot of a file. In the header, a button, labeled "Raw," outlined in dark orange.](/assets/images/help/repository/raw-file-button.png)
{% else %}
![Screenshot of a file. In the header, a button, labeled "Raw," outlined in dark orange.](/assets/images/enterprise/repository/raw-file-button.png)
{% endif %}
1. Optionally, to copy the raw file content, in the upper-right corner of the file view, click **{% octicon "copy" aria-label="Copy raw content" %}**. {% ifversion code-search-code-view %} To download the raw file, click **{% octicon "download" aria-label="Download raw file" %}**.{% endif %}
1. Optionally, to copy the raw file content, in the upper-right corner of the file view, click **{% octicon "copy" aria-label="Copy raw content" %}**. {% ifversion code-view-ui %} To download the raw file, click **{% octicon "download" aria-label="Download raw file" %}**.{% endif %}
## Viewing the line-by-line revision history for a file
@@ -44,7 +44,7 @@ Within the blame view, you can view the line-by-line revision history for an ent
{% data reusables.repositories.navigate-to-repo %}
1. Click to open the file whose line history you want to view.
{% ifversion code-search-code-view %}
{% ifversion code-view-ui %}
1. Above the file content, click **Blame**. This view gives you a line-by-line revision history, with the code in a file separated by commit. Each commit lists the author, commit description, and commit date.
1. To see versions of a file before a particular commit, click {% octicon "versions" aria-label="View blame prior to this change" %}. Alternatively, to see more detail about a particular commit, click the commit message.

View File

@@ -12,9 +12,31 @@ topics:
autogenerated: rest
---
## About the {% data variables.enterprise.management_console %}
## Deprecation of the Management Console endpoints
{% data reusables.enterprise_management_console.api-deprecation %}
The full functionality of the Management Console endpoints was added to the [Manage GHES](/rest/enterprise-admin/manage-ghes) endpoints in {% data variables.product.prodname_ghe_server %} version 3.12. With feature parity achieved, the Management Console API endpoints {% ifversion ghes < 3.14 %}will be{% else %}were{% endif %} deprecated in version 3.14.
{% ifversion management-console-manage-ghes-parity %}
To help you migrate, the mapping table below shows the equivalent Manage GHES operation for each Management Console operation.{% ifversion ghes < 3.14 %} Please migrate to the Manage GHES API endpoints as soon as possible.{% endif %}
| Purpose | Management Console API operation | Manage GHES API operation |
| ------------- | ------------- | - |
| Get the configuration status | `GET /setup/api/configcheck` | [`GET /manage/v1/config/apply`](/rest/enterprise-admin/manage-ghes#get-the-status-of-a-ghe-config-apply-run) |
| Start a configuration process | `POST /setup/api/configure` | [`POST /manage/v1/config/apply`](/rest/enterprise-admin/manage-ghes#trigger-a-ghe-config-apply-run) |
| Get the maintenance status | `GET /setup/api/maintenance` | [`GET /manage/v1/maintenance`](/rest/enterprise-admin/manage-ghes#get-the-status-of-maintenance-mode) |
| Enable or disable maintenance mode | `POST /setup/api/maintenance` | [`POST /manage/v1/maintenance`](/rest/enterprise-admin/manage-ghes#set-the-status-of-maintenance-mode) |
| Get settings | `GET /setup/api/settings` | [`GET /manage/v1/config/settings`](/rest/enterprise-admin/manage-ghes#get-the-ghes-settings) |
| Set settings | `PUT /setup/api/settings` | [`PUT /manage/v1/config/settings`](/rest/enterprise-admin/manage-ghes#set-settings) |
| Get all authorized SSH keys | `GET /setup/api/settings/authorized-keys` | [`GET /manage/v1/access/ssh`](/rest/enterprise-admin/manage-ghes#get-the-configured-ssh-keys) |
| Add an authorized SSH key | `POST /setup/api/settings/authorized-keys` | [`POST /manage/v1/access/ssh`](/rest/enterprise-admin/manage-ghes#set-a-new-ssh-key) |
| Remove an authorized SSH key | `DELETE /setup/api/settings/authorized-keys` | [`DELETE /manage/v1/access/ssh`](/rest/enterprise-admin/manage-ghes#delete-a-ssh-key) |
| Create a GitHub license | `POST /setup/api/start` | [`POST /manage/v1/config/init`](/rest/enterprise-admin/manage-ghes#initialize-instance-configuration-with-license-upload) |
| Upgrade a license | `POST /setup/api/upgrade` | [`PUT /manage/v1/config/license`](/rest/enterprise-admin/manage-ghes#upload-an-enterprise-license) |
{% endif %}
## About the {% data variables.enterprise.management_console %}
You should explicitly set the port number when making API calls to the Management Console. If TLS is enabled on your enterprise, the port number is `8443`. Otherwise, the port number is `8080`.

View File

@@ -1,10 +1,11 @@
---
title: REST API endpoints for organization roles
shortTitle: Organization roles
intro: 'Use the REST API to interact with organization roles.'
intro: Use the REST API to interact with organization roles.
versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖
fpt: '*'
ghec: '*'
ghes: '>=3.13'
topics:
- API
autogenerated: rest

View File

@@ -25,7 +25,7 @@ topics:
- To search globally across all of {% data variables.product.product_name %}, type what you're looking for into the search field at the top of any page, and choose "Search all of {% data variables.product.prodname_dotcom %}" in the search dropdown menu.
- To search within a particular repository or organization, navigate to the repository or organization page, type what you're looking for into the search field at the top of the page, and press **Enter**.
{% ifversion code-search-code-view %}You can also use suggestions and completions in the search bar to quickly find what you need.
{% ifversion code-search-upgrade %}You can also use suggestions and completions in the search bar to quickly find what you need.
- If you click on the search bar in the top navigation of GitHub.com, you will see a list of suggestions organized by category, including recent searches and suggested repositories, teams, and projects that you have access to.
- Clicking on any of the specific suggestions will take you directly to the page for that suggestion (for example, the repository or project page). If you click on a recent search, depending on the type of search, the search term will appear in the search bar or you will be taken to the search results page for the search term.
@@ -39,7 +39,7 @@ After typing a search query, you can press **Enter** to go to the full search re
**Notes:**
- {% data reusables.search.required_login %}
- {% data variables.product.prodname_pages %} sites are not searchable on {% data variables.product.product_name %}. However you can search the source content if it exists in the default branch of a repository, using code search. For more information, see "[AUTOTITLE]{% ifversion code-search-code-view %}(/search-github/github-code-search/understanding-github-code-search-syntax){% else %}(/search-github/searching-on-github/searching-code){% endif %}." For more information about {% data variables.product.prodname_pages %}, see "[AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages)"
- {% data variables.product.prodname_pages %} sites are not searchable on {% data variables.product.product_name %}. However you can search the source content if it exists in the default branch of a repository, using code search. For more information, see "[AUTOTITLE]{% ifversion code-search-upgrade %}(/search-github/github-code-search/understanding-github-code-search-syntax){% else %}(/search-github/searching-on-github/searching-code){% endif %}." For more information about {% data variables.product.prodname_pages %}, see "[AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages)"
- Currently our search doesn't support exact matching.{% ifversion ghes %}
- Whenever you are searching in code files, only the first two results in each file will be returned.{% endif %}
@@ -57,7 +57,7 @@ You can search for the following information across all repositories you can acc
- [Topics](/search-github/searching-on-github/searching-topics)
- [Issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt or ghec %}
- [Discussions](/search-github/searching-on-github/searching-discussions){% endif %}
- {% ifversion code-search-code-view %}[Code](/search-github/github-code-search/understanding-github-code-search-syntax){% else %}[Code](/search-github/searching-on-github/searching-code){% endif %}
- {% ifversion code-search-upgrade %}[Code](/search-github/github-code-search/understanding-github-code-search-syntax){% else %}[Code](/search-github/searching-on-github/searching-code){% endif %}
- [Commits](/search-github/searching-on-github/searching-commits)
- [Users](/search-github/searching-on-github/searching-users)
- [Packages](/search-github/searching-on-github/searching-for-packages)

View File

@@ -13,7 +13,7 @@ topics:
- GitHub search
---
{% ifversion code-search-code-view %}
{% ifversion code-search-upgrade %}
{% note %}
**Note:** Sorting search results is not supported for {% data variables.product.product_name %} code search. For more information on code search, see "[AUTOTITLE](/search-github/github-code-search/about-github-code-search)."

View File

@@ -26,7 +26,7 @@ There are some limits to the length of the queries when searching across {% data
- Queries longer than 256 characters are not supported
- You can't construct a query using more than five `AND`, `OR`, or `NOT` operators
Specific search types, such as code search, might have additional limitations. Check the documentation for these search types for more information. {% ifversion code-search-code-view %} For more information on code search limitations specifically, see "[AUTOTITLE](/search-github/github-code-search/about-github-code-search#limitations)."{% endif %}
Specific search types, such as code search, might have additional limitations. Check the documentation for these search types for more information. {% ifversion code-search-upgrade %} For more information on code search limitations specifically, see "[AUTOTITLE](/search-github/github-code-search/about-github-code-search#limitations)."{% endif %}
## Further reading

View File

@@ -15,7 +15,7 @@ topics:
shortTitle: Understand search syntax
---
{% ifversion code-search-code-view %}
{% ifversion code-search-upgrade %}
{% note %}
**Note:** The syntax below applies to non-code search. For more information on code search syntax, see "[AUTOTITLE](/search-github/github-code-search/understanding-github-code-search-syntax)."

View File

@@ -3,7 +3,7 @@ title: About GitHub Code Search
intro: 'You can search, navigate and understand code across {% data variables.product.prodname_dotcom %} with code search.'
allowTitleToDifferFromFilename: true
versions:
feature: code-search-code-view
feature: code-search-upgrade
topics:
- GitHub search
---

View File

@@ -3,7 +3,7 @@ title: GitHub Code Search
intro: 'Learn how to use code search to find, navigate, and understand code across {% data variables.product.prodname_dotcom %}.'
allowTitleToDifferFromFilename: true
versions:
feature: code-search-code-view
feature: code-search-upgrade
topics:
- GitHub search
children:

View File

@@ -4,7 +4,7 @@ shortTitle: Code search syntax
intro: 'You can build search queries for the results you want with specialized code qualifiers, regular expressions, and boolean operations.'
allowTitleToDifferFromFilename: true
versions:
feature: code-search-code-view
feature: code-search-upgrade
topics:
- GitHub search
---

View File

@@ -3,7 +3,7 @@ title: Using GitHub Code Search
intro: "You can use suggestions, completions and saved searches in the upgraded search interface to quickly find what you are looking for across {% data variables.product.prodname_dotcom_the_website %}."
allowTitleToDifferFromFilename: true
versions:
feature: code-search-code-view
feature: code-search-upgrade
topics:
- GitHub search
---

View File

@@ -1,6 +1,6 @@
---
title: Finding files on GitHub
intro: 'You can search for a file in a repository using the file finder. To search for a file in multiple repositories on {% data variables.product.product_name %}, use the {% ifversion code-search-code-view %}[`path` code search qualifier](/search-github/github-code-search/understanding-github-code-search-syntax#path-qualifier){% else %}[`filename` code search qualifier](/search-github/searching-on-github/searching-code#search-by-filename){% endif %}.'
intro: 'You can search for a file in a repository using the file finder. To search for a file in multiple repositories on {% data variables.product.product_name %}, use the {% ifversion code-search-upgrade %}[`path` code search qualifier](/search-github/github-code-search/understanding-github-code-search-syntax#path-qualifier){% else %}[`filename` code search qualifier](/search-github/searching-on-github/searching-code#search-by-filename){% endif %}.'
redirect_from:
- /articles/finding-files-on-github
- /github/searching-for-information-on-github/finding-files-on-github
@@ -16,14 +16,14 @@ topics:
**Tips:**
- By default, file finder results exclude some directories like `build`, `log`, `tmp`, and `vendor`. To search for files in these directories, {% ifversion code-search-code-view %}use the [`path` code search qualifier](/search-github/github-code-search/understanding-github-code-search-syntax#path-qualifier){% else %}use the [`filename` code search qualifier](/search-github/searching-on-github/searching-code#search-by-filename){% endif %}. Alternatively, you can customize which directories are excluded by default [using a `.gitattributes` file](#customizing-excluded-files).
- By default, file finder results exclude some directories like `build`, `log`, `tmp`, and `vendor`. To search for files in these directories, {% ifversion code-search-upgrade %}use the [`path` code search qualifier](/search-github/github-code-search/understanding-github-code-search-syntax#path-qualifier){% else %}use the [`filename` code search qualifier](/search-github/searching-on-github/searching-code#search-by-filename){% endif %}. Alternatively, you can customize which directories are excluded by default [using a `.gitattributes` file](#customizing-excluded-files).
- You can also open the file finder by pressing `t` on your keyboard. For more information, see "[AUTOTITLE](/get-started/accessibility/keyboard-shortcuts)."
{% endtip %}
## Using the file finder
{% ifversion code-search-code-view %}
{% ifversion code-view-ui %}
{% data reusables.repositories.navigate-to-repo %}
1. In the “Go to file” search bar, type the name of the file or directory you'd like to find.
![Screenshot of the main view for a repository. A search bar, labeled "Go to file", is outlined in dark orange.](/assets/images/help/repository/repository-main-page-go-to-file.png)

View File

@@ -1,6 +1,6 @@
---
title: Searching code {% ifversion code-search-code-view %}(legacy){% endif %}
intro: '{% ifversion code-search-code-view %}You only need to use the legacy code search syntax if you are using the code search API{% else %}You can search for code on {% data variables.product.product_name %} and narrow the results using these code search qualifiers in any combination{% endif %}.'
title: Searching code {% ifversion code-search-upgrade %}(legacy){% endif %}
intro: '{% ifversion code-search-upgrade %}You only need to use the legacy code search syntax if you are using the code search API{% else %}You can search for code on {% data variables.product.product_name %} and narrow the results using these code search qualifiers in any combination{% endif %}.'
redirect_from:
- /articles/searching-code
- /github/searching-for-information-on-github/searching-files-in-a-repository-for-exact-matches
@@ -15,7 +15,7 @@ versions:
topics:
- GitHub search
---
{% ifversion code-search-code-view %}
{% ifversion code-search-upgrade %}
{% note %}
**Note:** This article covers the syntax for legacy code search, which you should only need to use for the [REST API endpoint for searching code](/rest/search/search#search-code).

View File

@@ -36,7 +36,7 @@ With the `in` qualifier you can restrict your search to the repository name, rep
You can find a repository by searching for content in the repository's README file using the `in:readme` qualifier. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes)."
Besides using `in:readme`, it's not possible to find repositories by searching for specific content within the repository. To search for a specific file or content within a repository, you can use the file finder or code-specific search qualifiers. For more information, see "[AUTOTITLE](/search-github/searching-on-github/finding-files-on-github)" and "[AUTOTITLE]{% ifversion code-search-code-view %}(/search-github/github-code-search/understanding-github-code-search-syntax){% else %}(/search-github/searching-on-github/searching-code){% endif %}."
Besides using `in:readme`, it's not possible to find repositories by searching for specific content within the repository. To search for a specific file or content within a repository, you can use the file finder or code-specific search qualifiers. For more information, see "[AUTOTITLE](/search-github/searching-on-github/finding-files-on-github)" and "[AUTOTITLE]{% ifversion code-search-upgrade %}(/search-github/github-code-search/understanding-github-code-search-syntax){% else %}(/search-github/searching-on-github/searching-code){% endif %}."
| Qualifier | Example
| ------------- | -------------

View File

@@ -0,0 +1,6 @@
# Reference: #6672
# The new code search and symbols pane experience
# For the new code view UI, see code-view-ui.yml
versions:
fpt: '*'
ghec: '*'

View File

@@ -0,0 +1,7 @@
# Reference: #6672 and #13856
# The code view UI refresh in repositories
# For the new code search experience, see code-search-upgrade.yml
versions:
fpt: '*'
ghec: '*'
ghes: '>=3.13'

View File

@@ -0,0 +1,4 @@
# Migrating from projects (classic) requires enabling the option via feature preview
versions:
fpt: '*'
ghec: '*'

View File

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

View File

@@ -0,0 +1,137 @@
- title: Access to package version deletion
description: >-
This preview adds support for the DeletePackageVersion mutation which
enables deletion of private package versions.
toggled_by: ':package-deletes-preview'
announcement: null
updates: null
toggled_on:
- Mutation.deletePackageVersion
owning_teams:
- '@github/pe-package-registry'
- title: Deployments
description: >-
This preview adds support for deployments mutations and new deployments
features.
toggled_by: ':flash-preview'
announcement: null
updates: null
toggled_on:
- DeploymentStatus.environment
- Mutation.createDeploymentStatus
- CreateDeploymentStatusInput
- CreateDeploymentStatusPayload
- Mutation.createDeployment
- CreateDeploymentInput
- CreateDeploymentPayload
owning_teams:
- '@github/pages'
- title: >-
MergeInfoPreview - More detailed information about a pull request's merge
state.
description: >-
This preview adds support for accessing fields that provide more detailed
information about a pull request's merge state.
toggled_by: ':merge-info-preview'
announcement: null
updates: null
toggled_on:
- PullRequest.canBeRebased
- PullRequest.mergeStateStatus
owning_teams:
- '@github/pe-pull-requests'
- title: UpdateRefsPreview - Update multiple refs in a single operation.
description: This preview adds support for updating multiple refs in a single operation.
toggled_by: ':update-refs-preview'
announcement: null
updates: null
toggled_on:
- Mutation.updateRefs
- GitRefname
- RefUpdate
- UpdateRefsInput
- UpdateRefsPayload
owning_teams:
- '@github/repos'
- title: Access to a Repository's Dependency Graph
description: This preview adds support for reading a dependency graph for a repository.
toggled_by: ':hawkgirl-preview'
announcement: null
updates: null
toggled_on:
- DependencyGraphManifest
- Repository.dependencyGraphManifests
- DependencyGraphManifestEdge
- DependencyGraphManifestConnection
- DependencyGraphDependency
- DependencyGraphDependencyEdge
- DependencyGraphDependencyConnection
owning_teams:
- '@github/dependency-graph'
- title: Project Event Details
description: >-
This preview adds project, project card, and project column details to
project-related issue events.
toggled_by: ':starfox-preview'
announcement: null
updates: null
toggled_on:
- AddedToProjectEvent.project
- AddedToProjectEvent.projectCard
- AddedToProjectEvent.projectColumnName
- ConvertedNoteToIssueEvent.project
- ConvertedNoteToIssueEvent.projectCard
- ConvertedNoteToIssueEvent.projectColumnName
- MovedColumnsInProjectEvent.project
- MovedColumnsInProjectEvent.projectCard
- MovedColumnsInProjectEvent.projectColumnName
- MovedColumnsInProjectEvent.previousProjectColumnName
- RemovedFromProjectEvent.project
- RemovedFromProjectEvent.projectColumnName
owning_teams:
- '@github/github-projects'
- title: Labels Preview
description: >-
This preview adds support for adding, updating, creating and deleting
labels.
toggled_by: ':bane-preview'
announcement: null
updates: null
toggled_on:
- Mutation.createLabel
- CreateLabelPayload
- CreateLabelInput
- Mutation.deleteLabel
- DeleteLabelPayload
- DeleteLabelInput
- Mutation.updateLabel
- UpdateLabelPayload
- UpdateLabelInput
owning_teams:
- '@github/pe-pull-requests'
- title: Import Project
description: This preview adds support for importing projects.
toggled_by: ':slothette-preview'
announcement: null
updates: null
toggled_on:
- Mutation.importProject
owning_teams:
- '@github/pe-issues-projects'
- title: Team Review Assignments Preview
description: >-
This preview adds support for updating the settings for team review
assignment.
toggled_by: ':stone-crop-preview'
announcement: null
updates: null
toggled_on:
- Mutation.updateTeamReviewAssignment
- UpdateTeamReviewAssignmentInput
- TeamReviewAssignmentAlgorithm
- Team.reviewRequestDelegationEnabled
- Team.reviewRequestDelegationAlgorithm
- Team.reviewRequestDelegationMemberCount
- Team.reviewRequestDelegationNotifyTeam
owning_teams:
- '@github/pe-pull-requests'

View File

@@ -0,0 +1,170 @@
date: '2024-05-14'
release_candidate: true
deprecated: false
intro: |
> [!NOTE] Release candidate (RC) builds are intended solely for use in a test environment. Do not install an RC in a production environment.
>
> Do not upgrade to an RC from a supported, earlier version.
>
> If {% data variables.location.product_location %} is running an RC, you cannot upgrade to the general availability (GA) release. You also cannot upgrade with a hotpatch.
For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
sections:
# Remove section heading if the section contains no notes.
features:
# Remove a sub-section heading if the heading contains no notes. If sections
# that regularly recur are missing, add placeholders to this template.
- heading: Instance administration
notes:
# https://github.com/github/releases/issues/3816
- |
The root navigational experience for enterprise accounts lands all users on an "Enterprise Overview". From this page, enterprise owners can create a README for their enterprise, which will be visible internally to all enterprise members. The "Organization" page still exists and can be accessed from the left sidebar of the enterprise account.
# https://github.com/github/releases/issues/3842
- |
To improve the pre-flight checks experience, all pre-flight checks run even if one check fails. A consolidated report of the results is shown in the UI.
# https://github.com/github/releases/issues/3870
- |
The editor role for a Management Console user has been deprecated in the Manage GitHub Enterprise Server API.
# https://github.com/github/releases/issues/3765
- |
People deploying a GitHub Enterprise Server instance in AWS can now deploy in an environment that uses Instance Metadata Service Version 2 (IMDSv2).
# https://github.com/github/releases/issues/3887
- |
As part of the upgrade to GitHub Enterprise Server 3.13, Elasticsearch (ES) is upgraded from version 5.6.16 to 8.7.0. Upgrading platform components improves performance and security posture. For important upgrade considerations, see "[AUTOTITLE](/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/preparing-for-the-elasticsearch-upgrade)."
# https://github.com/github/releases/issues/3776
- |
To improve existing tooling for license handling, the `ghe-license` script handles all operations regarding the active license. Commands can be performed on new licenses without importing them first. The script allows direct application of the license without a full configuration run and avoids restarting the instance to reduce downtime. See "[AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-command-line/command-line-utilities#ghe-license)."
Administrators can upload the license to their instance using multiple interfaces, including the Management Console, Manage GHES API, CLI, or SSH. See "[AUTOTITLE](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."
- heading: Audit logs
notes:
# https://github.com/github/releases/issues/3724
- |
Enterprise and organization audit log events include the applicable SAML and SCIM identity data associated with the user. This data provides increased visibility into the identity of the user and enables logs from multiple systems to quickly and easily be linked using a common corporate identity. The SAML identity information displays in the `external_identity_nameid` field and the SCIM identity data displays in the `external_identity_username` field within the audit log payloads. For more information, see "[AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)."
- heading: GitHub Actions
notes:
# Required Actions Runner version
- |
{% data reusables.actions.actions-runner-release-note %}
# https://github.com/github/releases/issues/3822
- |
To ensure Actions runners are truly ephemeral and more secure, execution timeouts on self-hosted jobs are limited to 5 days. If a job reaches this limit, the job is terminated and fails to complete. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#usage-limits)."
- heading: Repositories
notes:
# https://github.com/github/releases/issues/2992
- |
Users can use repository properties to add meaningful metadata to repositories that simplifies repository classification, enhances discoverability, and seamlessly integrates with rulesets. For more information, see "[AUTOTITLE](/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization)."
# https://github.com/github/releases/issues/3849
- |
Users can browse and view code in a revamped experience for GitHub repositories, providing a tree pane for browsing files, fuzzy search for files, sticky code headers, and more.
# https://github.com/github/releases/issues/3550
- |
Users can migrate existing tag protection rules into repository rules. For more information, see "[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules#importing-tag-protection-rules-to-repository-rulesets)."
- heading: Projects
notes:
# https://github.com/github/releases/issues/3606
- |
Users can post status updates on their projects to share the current status, start date, and target date of the project itself. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects/sharing-project-updates)."
# https://github.com/github/releases/issues/3878
- |
Users can migrate their projects (classic) to the new Projects experience. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic)."
- heading: Pull requests
notes:
# https://github.com/github/releases/issues/3867
- |
Rebase commits are now created using the merge-ort strategy.
- heading: Secret scanning
notes:
# https://github.com/github/releases/issues/3566
- |
In the secret scanning list view, users can apply a filter to display alerts that are the result of having bypassed push protection. For more information, see "[AUTOTITLE](/code-security/secret-scanning/managing-alerts-from-secret-scanning)."
- heading: Code scanning
notes:
# https://github.com/github/releases/issues/3771
# https://github.com/github/releases/issues/3807
# https://github.com/github/releases/issues/3818
# https://github.com/github/releases/issues/3864
# https://github.com/github/releases/issues/3894
- |
The {% data variables.product.prodname_codeql %} action for code scanning analysis uses version 2.16.6 of the {% data variables.product.prodname_codeql_cli %} of the CodeQL CLI by default. See the [changelog](https://codeql.github.com/docs/codeql-overview/codeql-changelog/codeql-cli-2.16.6/) for this version.
# https://github.com/github/releases/issues/3526
- |
Users can enable code scanning on repositories even if they dont contain any code written in the [languages currently supported by CodeQL](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/). Default setup will automatically trigger the first scan when a supported language is detected on the default branch. For more information, see "[AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning)."
# https://github.com/github/releases/issues/3545
- |
Users can use CodeQL threat model settings for Java to adapt CodeQL's code scanning analysis to detect the most relevant security vulnerabilities in their code. This feature is in public beta and subject to change. For more information, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning)."
# https://github.com/github/releases/issues/3648
- |
To enable users to adopt the latest version of .NET / C# for their code base and continue using CodeQL to identify vulnerabilities, CodeQL code scanning supports C# 12 and .NET 8. For more information, see "[CodeQL 2.16.4](https://codeql.github.com/docs/codeql-overview/codeql-changelog/codeql-cli-2.16.4/#c-2)" in the CodeQL documentation.
- heading: Code security
notes:
# https://github.com/github/releases/issues/3333
# https://github.com/github/releases/issues/3778
# https://github.com/github/releases/issues/3779
- |
On the security overview dashboard, users can find detailed insights for the security alerts in an organization or enterprise, including trending data that tracks alert counts and activity over time and snapshot data that reflects the current state of the security landscape. Alerts are displayed for both GitHub's security features and third-party tools. Filters are available for the type and visibility of alerts, date range, repository custom properties, and more. The overview dashboard is in public beta and subject to change. For more information, see "[AUTOTITLE](/code-security/security-overview/viewing-security-insights)."
# https://github.com/github/releases/issues/3782
- |
Users can view trending data for the enablement of security features in an organization. In security overview for an organization, the "Enablement trends" view shows historical data for the activation of security features including Dependabot updates, code scanning alerts, and secret scanning alerts. This feature is in public beta and subject to change. For more information, see "[AUTOTITLE](/code-security/security-overview/assessing-adoption-code-security#viewing-enablement-trends-for-an-organization-beta)."
# https://github.com/github/releases/issues/3712
- |
For users who use `devcontainer.json` files to define development containers for repositories, Dependabot version updates can keep "features" defined for the dev container up to date. Once configured in `dependabot.yml`, Dependabot will open pull requests on a specified schedule to update the listed features to the latest version. Dependabot security updates for dev containers are not currently supported. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates#dev-containers)."
- heading: Authentication
notes:
# https://github.com/github/releases/issues/2473
- |
For enterprises or organizations that use an SSH certificate authority (CA) to provide SSH certificates to members, to protect against a security risk involving user renames, new SSH CAs that are uploaded to a GitHub Enterprise Server 3.13 instance can only be used to sign certificates that are set to expire. For new CAs, you must use the `-V` parameter with `ssh-keygen` to generate a certificate with a `valid-after` claim.
The `valid-after` claim allows GitHub to validate that the user named in the SSH certificate hasn't been renamed since the certificate was signed. CAs uploaded prior to version 3.13 are exempt from this requirement and can be used to sign certificates that do not expire. However, when you've ensured that your certificate signing process uses the `-V` flag, GitHub encourages you to upgrade existing certificates to enforce the expiration requirement. For more information, see "[AUTOTITLE](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities#upgrading-an-ssh-certificate-authority)" or "[AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#upgrading-an-ssh-certificate-authority)."
changes:
# https://github.com/github/releases/issues/3971
- |
TCP port 9103 is opened for future administrative features related to support for Prometheus scraping. The port has been open since GitHub Enterprise Server 3.12, but this change wasn't communicated at the time release notes for version 3.12 were first published.
# https://github.com/github/releases/issues/3940
- |
**Upcoming change:** In version 3.14 and later of GitHub Enterprise Server, for instances with GitHub Actions and GitHub Connect enabled, self-hosted runners that download actions from GitHub.com via GitHub Connect will need to allow access to the following new hosts.
- `ghcr.io`
- `*.actions.githubusercontent.com`
You can make this change to your firewall rules on version 3.13, or on a previous version of GitHub Enterprise Server. For a smooth upgrade to version 3.14, we recommend you make changes to your firewall rules now, as failing to do so will result in your runners being unable to download certain actions in version 3.14 and later.
# https://github.com/github/releases/issues/3443
- |
The "Create a reference" REST API endpoint is restricted from accepting POSTs from users and apps that only have permission to read and write packages. Previously, this endpoint accepted updates to both tags and branches.
known_issues:
# INCLUDE NOTES FOR RELEASE FROM "GHES Release Note Tracking" PROJECT'S "Known Issues" TAB
- |
Custom firewall rules are removed during the upgrade process.
- |
During the validation phase of a configuration run, a `No such object` error may occur for the Notebook and Viewscreen services. This error can be ignored as the services should still correctly start.
- |
If the root site administrator is locked out of the Management Console after failed login attempts, the account does not unlock automatically after the defined lockout time. Someone with administrative SSH access to the instance must unlock the account using the administrative shell. For more information, see "[AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/troubleshooting-access-to-the-management-console#unlocking-the-root-site-administrator-account)."
- |
On an instance with the HTTP `X-Forwarded-For` header configured for use behind a load balancer, all client IP addresses in the instance's audit log erroneously appear as 127.0.0.1.
- |
{% data reusables.release-notes.2023-12-backup-utils-exit-early-redis %}
- |
When enabling log forwarding, specific service logs, including babeld, are duplicated. For more information, see "[AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity-in-your-enterprise/log-forwarding#enabling-log-forwarding)."
deprecations:
# https://github.com/github/releases/issues/2732
- |
As part of sunsetting Subversion compatibility, Subversion support is now disabled by default. Subversion can be re-enabled in the 3.13 release series by setting `app.svnbridge.enabled = true`. In 3.14, subversion support will be permanently removed. For more information, see [Sunsetting Subversion support](https://github.blog/2023-01-20-sunsetting-subversion-support/) on the GitHub blog.
# https://github.com/github/releases/issues/3859
- |
The Manage GHES API reached feature parity with the Management Console API in GHES 3.12. As a result, we will deprecate the Management Console API in GitHub Enterprise Server 3.14. For information about updating tooling that relies on the Management Console API, see "[AUTOTITLE](/rest/enterprise-admin/management-console)."

View File

@@ -1 +1 @@
For self-hosted {% data variables.product.prodname_actions %} runners on this {% data variables.product.prodname_ghe_server %} release, the minimum required version of the {% data variables.product.prodname_actions %} Runner application is {% data variables.product.runner_controller_required_version %}. See the release notes for this version in the [`actions/runner` repository](https://github.com/actions/runner/releases/tag/v{% data variables.product.runner_controller_required_version %}) on {% data variables.product.prodname_dotcom_the_website %}. If your instance uses ephemeral self-hosted runners and you've disabled automatic updates, you must upgrade your runners to this version of the Runner application before upgrading your instance to this {% data variables.product.prodname_ghe_server %} release.
For self-hosted {% data variables.product.prodname_actions %} runners on this {% data variables.product.prodname_ghe_server %} release, the minimum required version of the {% data variables.product.prodname_actions %} Runner application is {% data variables.product.runner_required_version %}. See the release notes for this version in the [`actions/runner` repository](https://github.com/actions/runner/releases/tag/v{% data variables.product.runner_required_version %}) on {% data variables.product.prodname_dotcom_the_website %}. If your instance uses ephemeral self-hosted runners and you've disabled automatic updates, you must upgrade your runners to this version of the Runner application before upgrading your instance to this {% data variables.product.prodname_ghe_server %} release.

View File

@@ -1,4 +1,4 @@
1. Set an admin password that matches the password on the primary appliance and continue.
1. Click **Configure as Replica**.
1. Click {% ifversion ghes > 3.12 %}**Create a replica node**{% elsif ghes < 3.13 %}**Configure as Replica**{% endif %}.
1. Under "Add new SSH key", type your SSH key.
1. Click **Add key**.

View File

@@ -1,4 +1,4 @@
{% ifversion code-search-code-view %}
{% ifversion code-view-ui %}
1. Above the list of files, select the **Add file** {% octicon "triangle-down" aria-label="The downwards-facing triangle icon" %} dropdown menu, then click {% octicon "plus" aria-label="The plus sign icon" %} **Create new file**.
Alternatively, you can click {% octicon "plus" aria-label="The plus sign icon" %} in the file tree view on the left.

View File

@@ -1,4 +1,4 @@
{% ifversion code-search-code-view %}
{% ifversion code-view-ui %}
1. Above the new content, click **Preview**.
![Screenshot of a file in edit mode. Above the file's contents, a tab labeled "Preview" is outlined in dark orange.](/assets/images/help/repository/edit-readme-preview-changes.png)

View File

@@ -1,4 +1,4 @@
{% ifversion code-search-code-view %}
{% ifversion code-view-ui %}
1. Click **Commit changes...**
{% endif %}
1. In the "Commit message" field, type a short, meaningful commit message that describes the change you made to the file. You can attribute the commit to more than one author in the commit message. For more information, see "[AUTOTITLE](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)."

View File

@@ -1 +1 @@
1. Enable "Project migration" in feature preview. For more information, see "[AUTOTITLE](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."
{% ifversion projects-v2-migration-behind-feature-preview %}1. Enable "Project migration" in feature preview. For more information, see "[AUTOTITLE](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."{% endif %}

View File

@@ -1,6 +1,6 @@
When viewing a Markdown file, you can click {% ifversion code-search-code-view %}**Code**{% else %}{% octicon "code" aria-label="The code icon" %}{% endif %} at the top of the file to disable Markdown rendering and view the file's source instead.
When viewing a Markdown file, you can click {% ifversion code-view-ui %}**Code**{% else %}{% octicon "code" aria-label="The code icon" %}{% endif %} at the top of the file to disable Markdown rendering and view the file's source instead.
{% ifversion code-search-code-view %}
{% ifversion code-view-ui %}
![Screenshot of a Markdown file in a {% data variables.product.prodname_dotcom %} repository showing options for interacting with the file. A button, labeled "Code", is outlined in dark orange.](/assets/images/help/writing/display-markdown-as-source-global-nav-update.png)

View File

@@ -1,5 +1,5 @@
1. In the upper right corner of the file view, click {% octicon "pencil" aria-label="Edit file" %} to open the file editor.
{% ifversion code-search-code-view %}
{% ifversion code-view-ui %}
![Screenshot of a file. In the header, a button, labeled with a pencil icon, is outlined in dark orange.](/assets/images/help/repository/edit-file-edit-button.png)
{% else %}
![Screenshot of a file. In the header, a button, labeled with a pencil icon, is outlined in dark orange.](/assets/images/enterprise/repository/edit-file-edit-button.png)

View File

@@ -1,4 +1,4 @@
{% ifversion code-search-code-view %}
{% ifversion code-view-ui %}
1. From the file tree view on the left, select the {% octicon "git-branch" aria-hidden="true" %} branch dropdown menu, then click **View all branches**. You can also find the branch dropdown menu at the top of the integrated file editor.
![Screenshot of the file tree view for a repository. A dropdown menu for branches is expanded and outlined in dark orange.](/assets/images/help/repository/file-tree-view-branch-dropdown-expanded.png)

View File

@@ -2,6 +2,6 @@
**Note:** {% data variables.product.prodname_security_configurations_caps %} and {% data variables.product.prodname_global_settings %} are in beta and subject to change. To provide feedback on these features, see the [feedback discussion](https://github.com/orgs/community/discussions/114519).
To learn how to opt out of {% data variables.product.prodname_security_configurations %} and {% data variables.product.prodname_global_settings %}, see "[AUTOTITLE](/get-started/using-github/exploring-early-access-releases-with-feature-preview#exploring-beta-releases-with-feature-preview)."
{% ifversion fpt or ghec %} To learn how to opt out of {% data variables.product.prodname_security_configurations %} and {% data variables.product.prodname_global_settings %}, see "[AUTOTITLE](/get-started/using-github/exploring-early-access-releases-with-feature-preview#exploring-beta-releases-with-feature-preview)."{% endif %}
{% endnote %}

View File

@@ -136,7 +136,7 @@ prodname_unfurls: 'Content Attachments'
## Use this variable only when referring to GitHub Actions the product. When referring to the thing that someone creates using the product, call it an action (small a). See the terminology page of the Brand Guide for more.
prodname_actions: 'GitHub Actions'
prodname_actions_runner_controller: 'Actions Runner Controller'
runner_controller_required_version: >-
runner_required_version: >-
{% ifversion ghes < 3.10 %}2.303.0{% elsif ghes < 3.11 %}2.304.0{% elsif ghes < 3.12 %}2.309.0{% elsif ghes < 3.13 %}2.311.0{% elsif ghes < 3.14 %}2.314.1{% endif %}
# GitHub Debug

View File

@@ -155,7 +155,7 @@
"/en/enterprise/v4/object": "/en/enterprise-server/graphql/reference/objects",
"/en/enterprise/v4/object/actorlocation": "/en/enterprise-server/graphql/reference/objects#actorlocation",
"/en/enterprise/v4/object/addedtoprojectevent": "/en/enterprise-server/graphql/reference/objects#addedtoprojectevent",
"/en/enterprise/v4/previews": "/en/enterprise-server/graphql/overview/schema-previews",
"/en/enterprise/v4/previews": "/en/enterprise-server@3.12/graphql/overview/schema-previews",
"/en/enterprise/v4/public_schema": "/en/enterprise-server/graphql/overview/public-schema",
"/en/enterprise/v4/query": "/en/enterprise-server/graphql/reference/queries",
"/en/enterprise/v4/reference": "/en/enterprise-server/graphql/reference",
@@ -357,7 +357,7 @@
"/enterprise/v4/object": "/en/enterprise-server/graphql/reference/objects",
"/enterprise/v4/object/actorlocation": "/en/enterprise-server/graphql/reference/objects#actorlocation",
"/enterprise/v4/object/addedtoprojectevent": "/en/enterprise-server/graphql/reference/objects#addedtoprojectevent",
"/enterprise/v4/previews": "/en/enterprise-server/graphql/overview/schema-previews",
"/enterprise/v4/previews": "/en/enterprise-server@3.12/graphql/overview/schema-previews",
"/enterprise/v4/public_schema": "/en/enterprise-server/graphql/overview/public-schema",
"/enterprise/v4/query": "/en/enterprise-server/graphql/reference/queries",
"/enterprise/v4/reference": "/en/enterprise-server/graphql/reference",

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@@ -60,5 +60,5 @@
"2022-11-28"
]
},
"sha": "3a05345b2bd1336f25d515165c55ad48c7989954"
"sha": "64a193cd4bdda8028c54cb8558b4f5cb73bf83bc"
}

View File

@@ -0,0 +1,474 @@
---
upcoming_changes:
- location: LegacyMigration.uploadUrlTemplate
description: '`uploadUrlTemplate` will be removed. Use `uploadUrl` instead.'
reason:
'`uploadUrlTemplate` is being removed because it is not a standard URL and
adds an extra user step.'
date: '2019-04-01T00:00:00+00:00'
criticality: breaking
owner: tambling
- location: AssignedEvent.user
description: '`user` will be removed. Use the `assignee` field instead.'
reason: Assignees can now be mannequins.
date: '2020-01-01T00:00:00+00:00'
criticality: breaking
owner: tambling
- location: UnassignedEvent.user
description: '`user` will be removed. Use the `assignee` field instead.'
reason: Assignees can now be mannequins.
date: '2020-01-01T00:00:00+00:00'
criticality: breaking
owner: tambling
- location: Issue.timeline
description: '`timeline` will be removed. Use Issue.timelineItems instead.'
reason: '`timeline` will be removed'
date: '2020-10-01T00:00:00+00:00'
criticality: breaking
owner: mikesea
- location: PullRequest.timeline
description: '`timeline` will be removed. Use PullRequest.timelineItems instead.'
reason: '`timeline` will be removed'
date: '2020-10-01T00:00:00+00:00'
criticality: breaking
owner: mikesea
- location: MergeStateStatus.DRAFT
description: '`DRAFT` will be removed. Use PullRequest.isDraft instead.'
reason:
DRAFT state will be removed from this enum and `isDraft` should be used
instead
date: '2021-01-01T00:00:00+00:00'
criticality: breaking
owner: nplasterer
- location: PackageType.DOCKER
description: '`DOCKER` will be removed.'
reason:
DOCKER will be removed from this enum as this type will be migrated to only
be used by the Packages REST API.
date: '2021-06-21'
criticality: breaking
owner: reybard
- location: ReactionGroup.users
description: '`users` will be removed. Use the `reactors` field instead.'
reason: Reactors can now be mannequins, bots, and organizations.
date: '2021-10-01T00:00:00+00:00'
criticality: breaking
owner: synthead
- location: AddPullRequestToMergeQueueInput.branch
description: '`branch` will be removed.'
reason:
PRs are added to the merge queue for the base branch, the `branch` argument
is now a no-op
date: '2022-07-01T00:00:00+00:00'
criticality: breaking
owner: jhunschejones
- location: DependencyGraphDependency.packageLabel
description:
'`packageLabel` will be removed. Use normalized `packageName` field
instead.'
reason: '`packageLabel` will be removed.'
date: '2022-10-01T00:00:00+00:00'
criticality: breaking
owner: github/dependency_graph
- location: RemovePullRequestFromMergeQueueInput.branch
description: '`branch` will be removed.'
reason:
PRs are removed from the merge queue for the base branch, the `branch` argument
is now a no-op
date: '2022-10-01T00:00:00+00:00'
criticality: breaking
owner: jhunschejones
- location: PackageType.NPM
description: '`NPM` will be removed.'
reason:
NPM will be removed from this enum as this type will be migrated to only
be used by the Packages REST API.
date: '2022-11-21'
criticality: breaking
owner: s-anupam
- location: PackageType.NUGET
description: '`NUGET` will be removed.'
reason:
NUGET will be removed from this enum as this type will be migrated to only
be used by the Packages REST API.
date: '2022-11-21'
criticality: breaking
owner: s-anupam
- location: PackageType.RUBYGEMS
description: '`RUBYGEMS` will be removed.'
reason:
RUBYGEMS will be removed from this enum as this type will be migrated to
only be used by the Packages REST API.
date: '2022-12-28'
criticality: breaking
owner: ankitkaushal01
- location: Commit.changedFiles
description: '`changedFiles` will be removed. Use `changedFilesIfAvailable` instead.'
reason: '`changedFiles` will be removed.'
date: '2023-01-01T00:00:00+00:00'
criticality: breaking
owner: adamshwert
- location: ProjectV2View.visibleFields
description:
'`visibleFields` will be removed. Check out the `ProjectV2View#fields`
API as an example for the more capable alternative.'
reason:
The `ProjectV2View#visibleFields` API is deprecated in favour of the more
capable `ProjectV2View#fields` API.
date: '2023-01-01T00:00:00+00:00'
criticality: breaking
owner: mattruggio
- location: PackageType.MAVEN
description: '`MAVEN` will be removed.'
reason:
MAVEN will be removed from this enum as this type will be migrated to only
be used by the Packages REST API.
date: '2023-02-10'
criticality: breaking
owner: ankitkaushal01
- location: ProjectV2View.groupBy
description:
'`groupBy` will be removed. Check out the `ProjectV2View#group_by_fields`
API as an example for the more capable alternative.'
reason:
The `ProjectV2View#order_by` API is deprecated in favour of the more capable
`ProjectV2View#group_by_field` API.
date: '2023-04-01T00:00:00+00:00'
criticality: breaking
owner: alcere
- location: ProjectV2View.sortBy
description:
'`sortBy` will be removed. Check out the `ProjectV2View#sort_by_fields`
API as an example for the more capable alternative.'
reason:
The `ProjectV2View#sort_by` API is deprecated in favour of the more capable
`ProjectV2View#sort_by_fields` API.
date: '2023-04-01T00:00:00+00:00'
criticality: breaking
owner: traumverloren
- location: ProjectV2View.verticalGroupBy
description:
'`verticalGroupBy` will be removed. Check out the `ProjectV2View#vertical_group_by_fields`
API as an example for the more capable alternative.'
reason:
The `ProjectV2View#vertical_group_by` API is deprecated in favour of the
more capable `ProjectV2View#vertical_group_by_fields` API.
date: '2023-04-01T00:00:00+00:00'
criticality: breaking
owner: traumverloren
- location: Repository.squashPrTitleUsedAsDefault
description:
'`squashPrTitleUsedAsDefault` will be removed. Use `Repository.squashMergeCommitTitle`
instead.'
reason: '`squashPrTitleUsedAsDefault` will be removed.'
date: '2023-04-01T00:00:00+00:00'
criticality: breaking
owner: github/pull_requests
- location: Commit.pushedDate
description: '`pushedDate` will be removed.'
reason: '`pushedDate` is no longer supported.'
date: '2023-07-01T00:00:00+00:00'
criticality: breaking
owner: darthwillis
- location: ProjectV2ItemFieldGroup.field
description:
'`field` will be removed. Check out the `ProjectV2ItemFieldGroup#groupByField`
API as an example for the more capable alternative.'
reason:
The `ProjectV2ItemFieldGroup#field` API is deprecated in favour of the more
capable `ProjectV2ItemFieldGroup#groupByField` API.
date: '2023-07-01T00:00:00+00:00'
criticality: breaking
owner: stevepopovich
- location: AddPullRequestReviewCommentInput.body
description:
'`body` will be removed. use addPullRequestReviewThread or addPullRequestReviewThreadReply
instead'
reason: We are deprecating the addPullRequestReviewComment mutation
date: '2023-10-01T00:00:00+00:00'
criticality: breaking
owner: aharpole
- location: AddPullRequestReviewCommentInput.commitOID
description:
'`commitOID` will be removed. use addPullRequestReviewThread or addPullRequestReviewThreadReply
instead'
reason: We are deprecating the addPullRequestReviewComment mutation
date: '2023-10-01T00:00:00+00:00'
criticality: breaking
owner: aharpole
- location: AddPullRequestReviewCommentInput.inReplyTo
description:
'`inReplyTo` will be removed. use addPullRequestReviewThread or addPullRequestReviewThreadReply
instead'
reason: We are deprecating the addPullRequestReviewComment mutation
date: '2023-10-01T00:00:00+00:00'
criticality: breaking
owner: aharpole
- location: AddPullRequestReviewCommentInput.path
description:
'`path` will be removed. use addPullRequestReviewThread or addPullRequestReviewThreadReply
instead'
reason: We are deprecating the addPullRequestReviewComment mutation
date: '2023-10-01T00:00:00+00:00'
criticality: breaking
owner: aharpole
- location: AddPullRequestReviewCommentInput.position
description:
'`position` will be removed. use addPullRequestReviewThread or addPullRequestReviewThreadReply
instead'
reason: We are deprecating the addPullRequestReviewComment mutation
date: '2023-10-01T00:00:00+00:00'
criticality: breaking
owner: aharpole
- location: AddPullRequestReviewCommentInput.pullRequestId
description:
'`pullRequestId` will be removed. use addPullRequestReviewThread or
addPullRequestReviewThreadReply instead'
reason: We are deprecating the addPullRequestReviewComment mutation
date: '2023-10-01T00:00:00+00:00'
criticality: breaking
owner: aharpole
- location: AddPullRequestReviewCommentInput.pullRequestReviewId
description:
'`pullRequestReviewId` will be removed. use addPullRequestReviewThread
or addPullRequestReviewThreadReply instead'
reason: We are deprecating the addPullRequestReviewComment mutation
date: '2023-10-01T00:00:00+00:00'
criticality: breaking
owner: aharpole
- location: AddPullRequestReviewInput.comments
description: '`comments` will be removed. use the `threads` argument instead'
reason: We are deprecating comment fields that use diff-relative positioning
date: '2023-10-01T00:00:00+00:00'
criticality: breaking
owner: aharpole
- location: PullRequestReviewComment.originalPosition
description: '`originalPosition` will be removed.'
reason: We are phasing out diff-relative positioning for PR comments
date: '2023-10-01T00:00:00+00:00'
criticality: breaking
owner: aharpole
- location: PullRequestReviewComment.position
description:
'`position` will be removed. Use the `line` and `startLine` fields
instead, which are file line numbers instead of diff line numbers'
reason: We are phasing out diff-relative positioning for PR comments
date: '2023-10-01T00:00:00+00:00'
criticality: breaking
owner: aharpole
- location: CreateTeamDiscussionCommentInput.body
description:
'`body` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: CreateTeamDiscussionCommentInput.discussionId
description:
'`discussionId` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: CreateTeamDiscussionCommentPayload.teamDiscussionComment
description:
'`teamDiscussionComment` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: CreateTeamDiscussionInput.body
description:
'`body` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: CreateTeamDiscussionInput.private
description:
'`private` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: CreateTeamDiscussionInput.teamId
description:
'`teamId` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: CreateTeamDiscussionInput.title
description:
'`title` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: CreateTeamDiscussionPayload.teamDiscussion
description:
'`teamDiscussion` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussion.authorAssociation
description:
'`authorAssociation` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussion.bodyVersion
description:
'`bodyVersion` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussion.comments
description:
'`comments` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussion.commentsResourcePath
description:
'`commentsResourcePath` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussion.commentsUrl
description:
'`commentsUrl` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussion.isPinned
description:
'`isPinned` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussion.isPrivate
description:
'`isPrivate` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussion.number
description:
'`number` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussion.resourcePath
description:
'`resourcePath` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussion.team
description:
'`team` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussion.title
description:
'`title` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussion.url
description:
'`url` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussion.viewerCanPin
description:
'`viewerCanPin` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussionComment.authorAssociation
description:
'`authorAssociation` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussionComment.bodyVersion
description:
'`bodyVersion` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussionComment.discussion
description:
'`discussion` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussionComment.number
description:
'`number` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussionComment.resourcePath
description:
'`resourcePath` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges
- location: TeamDiscussionComment.url
description:
'`url` will be removed. Follow the guide at https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
to find a suitable replacement.'
reason: The Team Discussions feature is deprecated in favor of Organization Discussions.
date: '2024-07-01T00:00:00+00:00'
criticality: breaking
owner: deborah-digges

View File

@@ -0,0 +1,148 @@
[
{
"title": "Access to package version deletion preview",
"description": "This preview adds support for the DeletePackageVersion mutation which enables deletion of private package versions.",
"toggled_by": "package-deletes-preview",
"toggled_on": [
"Mutation.deletePackageVersion"
],
"owning_teams": [
"@github/pe-package-registry"
],
"accept_header": "application/vnd.github.package-deletes-preview+json",
"href": "/graphql/overview/schema-previews#access-to-package-version-deletion-preview"
},
{
"title": "Deployments preview",
"description": "This preview adds support for deployments mutations and new deployments features.",
"toggled_by": "flash-preview",
"toggled_on": [
"DeploymentStatus.environment",
"Mutation.createDeploymentStatus",
"Mutation.createDeployment"
],
"owning_teams": [
"@github/pages"
],
"accept_header": "application/vnd.github.flash-preview+json",
"href": "/graphql/overview/schema-previews#deployments-preview"
},
{
"title": "Merge info preview more detailed information about a pull request's merge state preview",
"description": "This preview adds support for accessing fields that provide more detailed information about a pull request's merge state.",
"toggled_by": "merge-info-preview",
"toggled_on": [
"PullRequest.canBeRebased",
"PullRequest.mergeStateStatus"
],
"owning_teams": [
"@github/pe-pull-requests"
],
"accept_header": "application/vnd.github.merge-info-preview+json",
"href": "/graphql/overview/schema-previews#merge-info-preview-more-detailed-information-about-a-pull-requests-merge-state-preview"
},
{
"title": "Update refs preview update multiple refs in a single operation preview",
"description": "This preview adds support for updating multiple refs in a single operation.",
"toggled_by": "update-refs-preview",
"toggled_on": [
"Mutation.updateRefs",
"GitRefname",
"RefUpdate"
],
"owning_teams": [
"@github/repos"
],
"accept_header": "application/vnd.github.update-refs-preview+json",
"href": "/graphql/overview/schema-previews#update-refs-preview-update-multiple-refs-in-a-single-operation-preview"
},
{
"title": "Access to a repository's dependency graph preview",
"description": "This preview adds support for reading a dependency graph for a repository.",
"toggled_by": "hawkgirl-preview",
"toggled_on": [
"DependencyGraphManifest",
"Repository.dependencyGraphManifests",
"DependencyGraphManifestEdge",
"DependencyGraphManifestConnection",
"DependencyGraphDependency",
"DependencyGraphDependencyEdge",
"DependencyGraphDependencyConnection"
],
"owning_teams": [
"@github/dependency-graph"
],
"accept_header": "application/vnd.github.hawkgirl-preview+json",
"href": "/graphql/overview/schema-previews#access-to-a-repositorys-dependency-graph-preview"
},
{
"title": "Project event details preview",
"description": "This preview adds project, project card, and project column details to project-related issue events.",
"toggled_by": "starfox-preview",
"toggled_on": [
"AddedToProjectEvent.project",
"AddedToProjectEvent.projectCard",
"AddedToProjectEvent.projectColumnName",
"ConvertedNoteToIssueEvent.project",
"ConvertedNoteToIssueEvent.projectCard",
"ConvertedNoteToIssueEvent.projectColumnName",
"MovedColumnsInProjectEvent.project",
"MovedColumnsInProjectEvent.projectCard",
"MovedColumnsInProjectEvent.projectColumnName",
"MovedColumnsInProjectEvent.previousProjectColumnName",
"RemovedFromProjectEvent.project",
"RemovedFromProjectEvent.projectColumnName"
],
"owning_teams": [
"@github/github-projects"
],
"accept_header": "application/vnd.github.starfox-preview+json",
"href": "/graphql/overview/schema-previews#project-event-details-preview"
},
{
"title": "Labels preview",
"description": "This preview adds support for adding, updating, creating and deleting labels.",
"toggled_by": "bane-preview",
"toggled_on": [
"Mutation.createLabel",
"Mutation.deleteLabel",
"Mutation.updateLabel"
],
"owning_teams": [
"@github/pe-pull-requests"
],
"accept_header": "application/vnd.github.bane-preview+json",
"href": "/graphql/overview/schema-previews#labels-preview"
},
{
"title": "Import project preview",
"description": "This preview adds support for importing projects.",
"toggled_by": "slothette-preview",
"toggled_on": [
"Mutation.importProject"
],
"owning_teams": [
"@github/pe-issues-projects"
],
"accept_header": "application/vnd.github.slothette-preview+json",
"href": "/graphql/overview/schema-previews#import-project-preview"
},
{
"title": "Team review assignments preview",
"description": "This preview adds support for updating the settings for team review assignment.",
"toggled_by": "stone-crop-preview",
"toggled_on": [
"Mutation.updateTeamReviewAssignment",
"TeamReviewAssignmentAlgorithm",
"Team.reviewRequestDelegationEnabled",
"Team.reviewRequestDelegationAlgorithm",
"Team.reviewRequestDelegationMemberCount",
"Team.reviewRequestDelegationNotifyTeam"
],
"owning_teams": [
"@github/pe-pull-requests"
],
"accept_header": "application/vnd.github.stone-crop-preview+json",
"href": "/graphql/overview/schema-previews#team-review-assignments-preview"
}
]

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@@ -0,0 +1,514 @@
{
"2024-07-01": [
{
"location": "TeamDiscussionComment.url",
"description": "<p><code>url</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "TeamDiscussionComment.resourcePath",
"description": "<p><code>resourcePath</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "TeamDiscussionComment.number",
"description": "<p><code>number</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "TeamDiscussionComment.discussion",
"description": "<p><code>discussion</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "TeamDiscussionComment.bodyVersion",
"description": "<p><code>bodyVersion</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "TeamDiscussionComment.authorAssociation",
"description": "<p><code>authorAssociation</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "TeamDiscussion.viewerCanPin",
"description": "<p><code>viewerCanPin</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "TeamDiscussion.url",
"description": "<p><code>url</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "TeamDiscussion.title",
"description": "<p><code>title</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "TeamDiscussion.team",
"description": "<p><code>team</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "TeamDiscussion.resourcePath",
"description": "<p><code>resourcePath</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "TeamDiscussion.number",
"description": "<p><code>number</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "TeamDiscussion.isPrivate",
"description": "<p><code>isPrivate</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "TeamDiscussion.isPinned",
"description": "<p><code>isPinned</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "TeamDiscussion.commentsUrl",
"description": "<p><code>commentsUrl</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "TeamDiscussion.commentsResourcePath",
"description": "<p><code>commentsResourcePath</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "TeamDiscussion.comments",
"description": "<p><code>comments</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "TeamDiscussion.bodyVersion",
"description": "<p><code>bodyVersion</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "TeamDiscussion.authorAssociation",
"description": "<p><code>authorAssociation</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "CreateTeamDiscussionPayload.teamDiscussion",
"description": "<p><code>teamDiscussion</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "CreateTeamDiscussionInput.title",
"description": "<p><code>title</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "CreateTeamDiscussionInput.teamId",
"description": "<p><code>teamId</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "CreateTeamDiscussionInput.private",
"description": "<p><code>private</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "CreateTeamDiscussionInput.body",
"description": "<p><code>body</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "CreateTeamDiscussionCommentPayload.teamDiscussionComment",
"description": "<p><code>teamDiscussionComment</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "CreateTeamDiscussionCommentInput.discussionId",
"description": "<p><code>discussionId</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
},
{
"location": "CreateTeamDiscussionCommentInput.body",
"description": "<p><code>body</code> will be removed. Follow the guide at <a href=\"https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/\">https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/</a> to find a suitable replacement.</p>",
"reason": "<p>The Team Discussions feature is deprecated in favor of Organization Discussions.</p>",
"date": "2024-07-01",
"criticality": "breaking",
"owner": "deborah-digges"
}
],
"2023-10-01": [
{
"location": "PullRequestReviewComment.position",
"description": "<p><code>position</code> will be removed. Use the <code>line</code> and <code>startLine</code> fields instead, which are file line numbers instead of diff line numbers</p>",
"reason": "<p>We are phasing out diff-relative positioning for PR comments</p>",
"date": "2023-10-01",
"criticality": "breaking",
"owner": "aharpole"
},
{
"location": "PullRequestReviewComment.originalPosition",
"description": "<p><code>originalPosition</code> will be removed.</p>",
"reason": "<p>We are phasing out diff-relative positioning for PR comments</p>",
"date": "2023-10-01",
"criticality": "breaking",
"owner": "aharpole"
},
{
"location": "AddPullRequestReviewInput.comments",
"description": "<p><code>comments</code> will be removed. use the <code>threads</code> argument instead</p>",
"reason": "<p>We are deprecating comment fields that use diff-relative positioning</p>",
"date": "2023-10-01",
"criticality": "breaking",
"owner": "aharpole"
},
{
"location": "AddPullRequestReviewCommentInput.pullRequestReviewId",
"description": "<p><code>pullRequestReviewId</code> will be removed. use addPullRequestReviewThread or addPullRequestReviewThreadReply instead</p>",
"reason": "<p>We are deprecating the addPullRequestReviewComment mutation</p>",
"date": "2023-10-01",
"criticality": "breaking",
"owner": "aharpole"
},
{
"location": "AddPullRequestReviewCommentInput.pullRequestId",
"description": "<p><code>pullRequestId</code> will be removed. use addPullRequestReviewThread or addPullRequestReviewThreadReply instead</p>",
"reason": "<p>We are deprecating the addPullRequestReviewComment mutation</p>",
"date": "2023-10-01",
"criticality": "breaking",
"owner": "aharpole"
},
{
"location": "AddPullRequestReviewCommentInput.position",
"description": "<p><code>position</code> will be removed. use addPullRequestReviewThread or addPullRequestReviewThreadReply instead</p>",
"reason": "<p>We are deprecating the addPullRequestReviewComment mutation</p>",
"date": "2023-10-01",
"criticality": "breaking",
"owner": "aharpole"
},
{
"location": "AddPullRequestReviewCommentInput.path",
"description": "<p><code>path</code> will be removed. use addPullRequestReviewThread or addPullRequestReviewThreadReply instead</p>",
"reason": "<p>We are deprecating the addPullRequestReviewComment mutation</p>",
"date": "2023-10-01",
"criticality": "breaking",
"owner": "aharpole"
},
{
"location": "AddPullRequestReviewCommentInput.inReplyTo",
"description": "<p><code>inReplyTo</code> will be removed. use addPullRequestReviewThread or addPullRequestReviewThreadReply instead</p>",
"reason": "<p>We are deprecating the addPullRequestReviewComment mutation</p>",
"date": "2023-10-01",
"criticality": "breaking",
"owner": "aharpole"
},
{
"location": "AddPullRequestReviewCommentInput.commitOID",
"description": "<p><code>commitOID</code> will be removed. use addPullRequestReviewThread or addPullRequestReviewThreadReply instead</p>",
"reason": "<p>We are deprecating the addPullRequestReviewComment mutation</p>",
"date": "2023-10-01",
"criticality": "breaking",
"owner": "aharpole"
},
{
"location": "AddPullRequestReviewCommentInput.body",
"description": "<p><code>body</code> will be removed. use addPullRequestReviewThread or addPullRequestReviewThreadReply instead</p>",
"reason": "<p>We are deprecating the addPullRequestReviewComment mutation</p>",
"date": "2023-10-01",
"criticality": "breaking",
"owner": "aharpole"
}
],
"2023-07-01": [
{
"location": "ProjectV2ItemFieldGroup.field",
"description": "<p><code>field</code> will be removed. Check out the <code>ProjectV2ItemFieldGroup#groupByField</code> API as an example for the more capable alternative.</p>",
"reason": "<p>The <code>ProjectV2ItemFieldGroup#field</code> API is deprecated in favour of the more capable <code>ProjectV2ItemFieldGroup#groupByField</code> API.</p>",
"date": "2023-07-01",
"criticality": "breaking",
"owner": "stevepopovich"
},
{
"location": "Commit.pushedDate",
"description": "<p><code>pushedDate</code> will be removed.</p>",
"reason": "<p><code>pushedDate</code> is no longer supported.</p>",
"date": "2023-07-01",
"criticality": "breaking",
"owner": "darthwillis"
}
],
"2023-04-01": [
{
"location": "Repository.squashPrTitleUsedAsDefault",
"description": "<p><code>squashPrTitleUsedAsDefault</code> will be removed. Use <code>Repository.squashMergeCommitTitle</code> instead.</p>",
"reason": "<p><code>squashPrTitleUsedAsDefault</code> will be removed.</p>",
"date": "2023-04-01",
"criticality": "breaking",
"owner": "github/pull_requests"
},
{
"location": "ProjectV2View.verticalGroupBy",
"description": "<p><code>verticalGroupBy</code> will be removed. Check out the <code>ProjectV2View#vertical_group_by_fields</code> API as an example for the more capable alternative.</p>",
"reason": "<p>The <code>ProjectV2View#vertical_group_by</code> API is deprecated in favour of the more capable <code>ProjectV2View#vertical_group_by_fields</code> API.</p>",
"date": "2023-04-01",
"criticality": "breaking",
"owner": "traumverloren"
},
{
"location": "ProjectV2View.sortBy",
"description": "<p><code>sortBy</code> will be removed. Check out the <code>ProjectV2View#sort_by_fields</code> API as an example for the more capable alternative.</p>",
"reason": "<p>The <code>ProjectV2View#sort_by</code> API is deprecated in favour of the more capable <code>ProjectV2View#sort_by_fields</code> API.</p>",
"date": "2023-04-01",
"criticality": "breaking",
"owner": "traumverloren"
},
{
"location": "ProjectV2View.groupBy",
"description": "<p><code>groupBy</code> will be removed. Check out the <code>ProjectV2View#group_by_fields</code> API as an example for the more capable alternative.</p>",
"reason": "<p>The <code>ProjectV2View#order_by</code> API is deprecated in favour of the more capable <code>ProjectV2View#group_by_field</code> API.</p>",
"date": "2023-04-01",
"criticality": "breaking",
"owner": "alcere"
}
],
"2023-02-10": [
{
"location": "PackageType.MAVEN",
"description": "<p><code>MAVEN</code> will be removed.</p>",
"reason": "<p>MAVEN will be removed from this enum as this type will be migrated to only be used by the Packages REST API.</p>",
"date": "2023-02-10",
"criticality": "breaking",
"owner": "ankitkaushal01"
}
],
"2023-01-01": [
{
"location": "ProjectV2View.visibleFields",
"description": "<p><code>visibleFields</code> will be removed. Check out the <code>ProjectV2View#fields</code> API as an example for the more capable alternative.</p>",
"reason": "<p>The <code>ProjectV2View#visibleFields</code> API is deprecated in favour of the more capable <code>ProjectV2View#fields</code> API.</p>",
"date": "2023-01-01",
"criticality": "breaking",
"owner": "mattruggio"
},
{
"location": "Commit.changedFiles",
"description": "<p><code>changedFiles</code> will be removed. Use <code>changedFilesIfAvailable</code> instead.</p>",
"reason": "<p><code>changedFiles</code> will be removed.</p>",
"date": "2023-01-01",
"criticality": "breaking",
"owner": "adamshwert"
}
],
"2022-12-28": [
{
"location": "PackageType.RUBYGEMS",
"description": "<p><code>RUBYGEMS</code> will be removed.</p>",
"reason": "<p>RUBYGEMS will be removed from this enum as this type will be migrated to only be used by the Packages REST API.</p>",
"date": "2022-12-28",
"criticality": "breaking",
"owner": "ankitkaushal01"
}
],
"2022-11-21": [
{
"location": "PackageType.NUGET",
"description": "<p><code>NUGET</code> will be removed.</p>",
"reason": "<p>NUGET will be removed from this enum as this type will be migrated to only be used by the Packages REST API.</p>",
"date": "2022-11-21",
"criticality": "breaking",
"owner": "s-anupam"
},
{
"location": "PackageType.NPM",
"description": "<p><code>NPM</code> will be removed.</p>",
"reason": "<p>NPM will be removed from this enum as this type will be migrated to only be used by the Packages REST API.</p>",
"date": "2022-11-21",
"criticality": "breaking",
"owner": "s-anupam"
}
],
"2022-10-01": [
{
"location": "RemovePullRequestFromMergeQueueInput.branch",
"description": "<p><code>branch</code> will be removed.</p>",
"reason": "<p>PRs are removed from the merge queue for the base branch, the <code>branch</code> argument is now a no-op</p>",
"date": "2022-10-01",
"criticality": "breaking",
"owner": "jhunschejones"
},
{
"location": "DependencyGraphDependency.packageLabel",
"description": "<p><code>packageLabel</code> will be removed. Use normalized <code>packageName</code> field instead.</p>",
"reason": "<p><code>packageLabel</code> will be removed.</p>",
"date": "2022-10-01",
"criticality": "breaking",
"owner": "github/dependency_graph"
}
],
"2022-07-01": [
{
"location": "AddPullRequestToMergeQueueInput.branch",
"description": "<p><code>branch</code> will be removed.</p>",
"reason": "<p>PRs are added to the merge queue for the base branch, the <code>branch</code> argument is now a no-op</p>",
"date": "2022-07-01",
"criticality": "breaking",
"owner": "jhunschejones"
}
],
"2021-10-01": [
{
"location": "ReactionGroup.users",
"description": "<p><code>users</code> will be removed. Use the <code>reactors</code> field instead.</p>",
"reason": "<p>Reactors can now be mannequins, bots, and organizations.</p>",
"date": "2021-10-01",
"criticality": "breaking",
"owner": "synthead"
}
],
"2021-06-21": [
{
"location": "PackageType.DOCKER",
"description": "<p><code>DOCKER</code> will be removed.</p>",
"reason": "<p>DOCKER will be removed from this enum as this type will be migrated to only be used by the Packages REST API.</p>",
"date": "2021-06-21",
"criticality": "breaking",
"owner": "reybard"
}
],
"2021-01-01": [
{
"location": "MergeStateStatus.DRAFT",
"description": "<p><code>DRAFT</code> will be removed. Use PullRequest.isDraft instead.</p>",
"reason": "<p>DRAFT state will be removed from this enum and <code>isDraft</code> should be used instead</p>",
"date": "2021-01-01",
"criticality": "breaking",
"owner": "nplasterer"
}
],
"2020-10-01": [
{
"location": "PullRequest.timeline",
"description": "<p><code>timeline</code> will be removed. Use PullRequest.timelineItems instead.</p>",
"reason": "<p><code>timeline</code> will be removed</p>",
"date": "2020-10-01",
"criticality": "breaking",
"owner": "mikesea"
},
{
"location": "Issue.timeline",
"description": "<p><code>timeline</code> will be removed. Use Issue.timelineItems instead.</p>",
"reason": "<p><code>timeline</code> will be removed</p>",
"date": "2020-10-01",
"criticality": "breaking",
"owner": "mikesea"
}
],
"2020-01-01": [
{
"location": "UnassignedEvent.user",
"description": "<p><code>user</code> will be removed. Use the <code>assignee</code> field instead.</p>",
"reason": "<p>Assignees can now be mannequins.</p>",
"date": "2020-01-01",
"criticality": "breaking",
"owner": "tambling"
},
{
"location": "AssignedEvent.user",
"description": "<p><code>user</code> will be removed. Use the <code>assignee</code> field instead.</p>",
"reason": "<p>Assignees can now be mannequins.</p>",
"date": "2020-01-01",
"criticality": "breaking",
"owner": "tambling"
}
],
"2019-04-01": [
{
"location": "LegacyMigration.uploadUrlTemplate",
"description": "<p><code>uploadUrlTemplate</code> will be removed. Use <code>uploadUrl</code> instead.</p>",
"reason": "<p><code>uploadUrlTemplate</code> is being removed because it is not a standard URL and adds an extra user step.</p>",
"date": "2019-04-01",
"criticality": "breaking",
"owner": "tambling"
}
]
}

View File

@@ -246,7 +246,7 @@
"/v4/previews": "/graphql/overview/schema-previews",
"/free-pro-team@latest/v4/previews": "/graphql/overview/schema-previews",
"/enterprise/graphql/overview/schema-previews": "/enterprise-server@latest/graphql/overview/schema-previews",
"/enterprise/v4/previews": "/enterprise-server@latest/graphql/overview/schema-previews",
"/enterprise/v4/previews": "/enterprise-server@3.12/graphql/overview/schema-previews",
"/enterprise/2.20/graphql/overview/schema-previews": "/enterprise-server@2.20/graphql/overview/schema-previews",
"/enterprise-server@2.20/v4/previews": "/enterprise-server@2.20/graphql/overview/schema-previews",
"/enterprise/2.20/v4/previews": "/enterprise-server@2.20/graphql/overview/schema-previews",
@@ -4194,4 +4194,4 @@
"/v4/union/searchresultitem": "/graphql/reference/unions#searchresultitem",
"/v4/union/sponsor": "/graphql/reference/unions#sponsor",
"/v4/union/statuscheckrollupcontext": "/graphql/reference/unions#statuscheckrollupcontext"
}
}

File diff suppressed because one or more lines are too long

View File

@@ -17,6 +17,9 @@
],
"ghes-3.12": [
"2022-11-28"
],
"ghes-3.13": [
"2022-11-28"
]
},
"versionMapping": {
@@ -44,5 +47,5 @@
]
}
},
"sha": "3a05345b2bd1336f25d515165c55ad48c7989954"
"sha": "64a193cd4bdda8028c54cb8558b4f5cb73bf83bc"
}

View File

@@ -9,13 +9,13 @@ export const dates = JSON.parse(await fs.readFile('src/ghes-releases/lib/enterpr
// enterprise-releases/docs/supported-versions.md#release-lifecycle-dates
// Some frontmatter may contain the upcoming GHES release number
export const next = '3.13'
export const nextNext = '3.14'
export const next = '3.14'
export const nextNext = '3.15'
export const supported = ['3.12', '3.11', '3.10', '3.9']
export const supported = ['3.13', '3.12', '3.11', '3.10', '3.9']
// Edit this to `null` when it's no longer the release candidate
export const releaseCandidate = null
export const releaseCandidate = '3.13'
// Ensure that:
// "next" is ahead of "latest" by one minor or major release.

File diff suppressed because it is too large Load Diff

View File

@@ -1,3 +1,3 @@
{
"sha": "3a05345b2bd1336f25d515165c55ad48c7989954"
"sha": "64a193cd4bdda8028c54cb8558b4f5cb73bf83bc"
}