GitHub Enterprise Server 3.16 release candidate (#54227)
Co-authored-by: Pallavi <96553709+pallsama@users.noreply.github.com> Co-authored-by: Andrey Bazhutkin <andrba@github.com> Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com> Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com> Co-authored-by: Roniece Ricardo <33437850+RonRicardo@users.noreply.github.com> Co-authored-by: docs-bot <77750099+docs-bot@users.noreply.github.com> Co-authored-by: Vanessa <vgrl@github.com> Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com> Co-authored-by: Courtney Claessens <courtneycl@github.com> Co-authored-by: isaacmbrown <isaacmbrown@github.com>
This commit is contained in:
Rachael Rose Renk
committed by
GitHub
GitHub
parent
4b00ac42cd
commit
adf1158e5c
@@ -134,7 +134,7 @@ $ ghe-config app.github.rate-limiting-exempt-users "hubot github-actions[bot]"
|
||||
|
||||
### ghe-config-apply
|
||||
|
||||
This utility applies {% data variables.enterprise.management_console %} settings, reloads system services, prepares a storage device, reloads application services, and runs any pending database migrations. It is equivalent to clicking **Save settings** in the {% data variables.enterprise.management_console %}'s web UI or to sending a POST request to {% ifversion management-console-manage-ghes-parity %}[the `/manage/v1/config/apply` endpoint](/rest/enterprise-admin/manage-ghes#trigger-a-ghe-config-apply-run){% else %}[the `/setup/api/configure` endpoint](/rest/enterprise-admin/management-console){% endif %}.
|
||||
This utility applies {% data variables.enterprise.management_console %} settings, reloads system services, prepares a storage device, reloads application services, and runs any pending database migrations. It is equivalent to clicking **Save settings** in the {% data variables.enterprise.management_console %}'s web UI or to sending a POST request to {% ifversion management-console-manage-ghes-parity %}[the `/manage/v1/config/apply` endpoint](/rest/enterprise-admin/manage-ghes#trigger-a-ghe-config-apply-run){% else %}[the `/setup/api/configure` endpoint](/rest/enterprise-admin/management-console){% endif %}. {% ifversion ghes > 3.15 %} Starting in version 3.16, this utility applies configuration changes conditionally to relevant settings. You can force it to run unconditionally by using `-f` flag. {% endif %}
|
||||
|
||||
```shell
|
||||
ghe-config-apply
|
||||
|
||||
@@ -69,6 +69,7 @@ For instances with {% data variables.product.prodname_actions %} enabled, self-h
|
||||
|
||||
| {% data variables.product.prodname_ghe_server %} version | Minimum Runner version |
|
||||
| ------------------------------------------------- | ---------------------- |
|
||||
| 3.16 | 2.321.0 ([release notes](https://github.com/actions/runner/releases/tag/v2.321.0)) |
|
||||
| 3.15 | 2.319.1 ([release notes](https://github.com/actions/runner/releases/tag/v2.319.1)) |
|
||||
| 3.14 | 2.317.0 ([release notes](https://github.com/actions/runner/releases/tag/v2.317.0)) |
|
||||
| 3.13 | 2.314.1 ([release notes](https://github.com/actions/runner/releases/tag/v2.314.1)) |
|
||||
|
||||
@@ -30,6 +30,12 @@ Your instance uses metrics from `collectd` to display graphs in the {% data vari
|
||||
|
||||
You can review a list of the metrics that `collectd` gathers on {% data variables.location.product_location %}. For more information, see [AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/collectd-metrics-for-github-enterprise-server).
|
||||
|
||||
{% ifversion prometheus-metrics-exporter %}
|
||||
|
||||
> [!TIP] In {% data variables.product.prodname_ghe_server %} 3.16, support was added for exporting `collectd` metrics in Prometheus format. This update does not change the existing metrics stack in the appliance but provides an easier way to ingest metrics into an observability platform by supporting the Prometheus protocol. An additional option is available to expose collectd metrics in Prometheus format with an endpoint. See [AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/exporting-and-scraping-prometheus-metrics).
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Set up an external `collectd` server
|
||||
|
||||
If you haven't already set up an external `collectd` server, you will need to do so before enabling `collectd` forwarding on {% data variables.location.product_location %}. Your `collectd` server must be running `collectd` version 5.x or higher.
|
||||
|
||||
@@ -0,0 +1,78 @@
|
||||
---
|
||||
title: Exporting and scraping Prometheus metrics
|
||||
shortTitle: Export and scrape Prometheus metrics
|
||||
intro: "{% data variables.product.prodname_ghe_server %} provides Prometheus-compatible metrics by transforming `collectd` data. These metrics can be scraped from a dedicated endpoint, allowing integration with observability and monitoring tools for performance insights."
|
||||
versions:
|
||||
feature: prometheus-metrics-exporter
|
||||
type: how_to
|
||||
topics:
|
||||
- Enterprise
|
||||
- Fundamentals
|
||||
- Infrastructure
|
||||
- Monitoring
|
||||
- Performance
|
||||
---
|
||||
|
||||
{% data variables.product.prodname_ghe_server %} includes a Prometheus metrics exporter to simplify observability and monitoring. This feature allows metrics to be scraped directly from the appliance, eliminating the need to forward `collectd` metrics to an external `collectd` server for transformation before sending them to a Prometheus system. By supporting Prometheus-compatible metrics natively, the exporter enables seamless integration with external monitoring dashboards and alerting systems.
|
||||
|
||||
## Enabling Prometheus metrics exporter and scraping metrics
|
||||
|
||||
By default, the Prometheus metrics exporter and scraping are disabled. Enabling the exporter for `collectd` metrics opens the metrics endpoint (also knows as `scrape endpoint`) at `http(s)://HOSTNAME:9103`. Ensure that firewall rules allow traffic on port 9103.
|
||||
|
||||
You can enable the Prometheus metrics exporter using the {% data variables.enterprise.management_console %}, the command line interface within the appliance, or the API.
|
||||
|
||||
### Enabling using the {% data variables.enterprise.management_console %}
|
||||
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %}
|
||||
{% data reusables.enterprise_site_admin_settings.management-console %}
|
||||
1. In the monitoring settings, select **Enable prometheus**.
|
||||
1. In the **Trusted IPv4/IPv6 addresses or CIDR blocks in a comma-separated list** field, type the comma-separated list of ip addresses or CIDR blocks. An example: `10.0.0.1, 192.168.1.0/8`. If this field is left empty, then scraping requests from any source IP will be accepted.
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
### Enabling via the command line interface
|
||||
|
||||
To enable the Prometheus metrics exporter, SSH into the {% data variables.product.prodname_ghe_server %} appliance and run the following commands:
|
||||
|
||||
```shell
|
||||
ghe-config app.prometheus.enabled true
|
||||
# Specify a comma-separated list of trusted IPv4/IPv6 addresses or CIDR blocks.
|
||||
ghe-config app.prometheus.trusted-ips "10.0.0.1, 192.168.1.0/8"
|
||||
ghe-config-apply
|
||||
```
|
||||
|
||||
### Enabling using the API
|
||||
|
||||
You can enable the Prometheus metrics exporter using the API by sending a `PUT` request to update the configuration settings.
|
||||
|
||||
```shell
|
||||
curl -L -H "Content-Type: application/json" -X PUT -u "api_key:xxxxxxx" https://<hostname>/manage/v1/config/settings -d '{"prometheus": {"enabled": true, "trusted_ips": "10.0.0.1, 192.168.1.0/8"}}'
|
||||
```
|
||||
|
||||
## Verifying the Prometheus metrics exporter is enabled
|
||||
|
||||
To verify that the Prometheus metrics exporter is enabled, use `curl` to query the `/metrics` endpoint on port 9103. For more information about the administrative ports, see [AUTOTITLE](/admin/configuring-settings/configuring-network-settings/network-ports#administrative-ports).
|
||||
|
||||
```shell
|
||||
curl localhost:9103/metrics
|
||||
```
|
||||
|
||||
If successful, the response will include metrics with the `collectd_` prefix.
|
||||
|
||||
## Configuring your external Prometheus server
|
||||
|
||||
To scrape exported metrics from {% data variables.product.prodname_ghe_server %}, add a scraping configuration to the `prometheus.yaml` file on your external Prometheus server.
|
||||
|
||||
```yaml
|
||||
- job_name: "ghes-prom-agent"
|
||||
scrape_interval: 10s
|
||||
static_configs:
|
||||
- targets: ["http(s)://HOSTNAME:9103/metrics"]
|
||||
```
|
||||
|
||||
## Support for the darkshipped Prometheus metrics exporter
|
||||
|
||||
If you have been using the Prometheus metrics exporter since it was darkshipped in {% data variables.product.prodname_ghe_server %} 3.12, it will continue to work after upgrading to 3.16. In this version, you now have the option to specify trusted IPs for scraping requests.
|
||||
|
||||
## Sharing feedback
|
||||
|
||||
You can share your feedback on the Prometheus metrics exporter and scraping functionality with {% data variables.product.company_short %}. For help with questions or issues, visit {% data variables.contact.contact_ent_support %}.
|
||||
@@ -23,6 +23,6 @@ children:
|
||||
- /about-system-logs
|
||||
- /troubleshooting-resource-allocation-problems
|
||||
- /generating-a-health-check-for-your-enterprise
|
||||
- /exporting-and-scraping-prometheus-metrics
|
||||
shortTitle: Monitor your instance
|
||||
---
|
||||
|
||||
|
||||
@@ -27,3 +27,13 @@ Simple Network Management Protocol (SNMP) is a widely supported method of monito
|
||||
collectd is an open source statistics collection and reporting daemon with built-in support for writing to RRD files. Statistics on CPU utilization, memory and disk consumption, network interface traffic and errors, and system load can be forwarded to an external collectd server where graphs, analysis, and alerting may be configured using a wide range of available tools and plugins. To configure `collectd` forwarding, see [AUTOTITLE](/admin/enterprise-management/monitoring-your-appliance/configuring-collectd).
|
||||
|
||||
Additionally, the monitoring tools built into underlying virtualization platforms may also be used for basic monitoring and alerting of system resources. For more information, see [Amazon CloudWatch](https://aws.amazon.com/cloudwatch/) and [VMware vSphere](https://docs.vmware.com/en/VMware-vSphere/index.html) documentation.
|
||||
|
||||
{% ifversion prometheus-metrics-exporter %}
|
||||
|
||||
## About the Prometheus metrics exporter
|
||||
|
||||
The Prometheus metrics exporter allows you to integrate {% data variables.product.prodname_ghe_server %} metrics into your observability pipeline and tooling. You can scrape metrics in a Prometheus-compatible format via the `/metrics` API at regular intervals and feed them into your observability system.
|
||||
|
||||
To configure the Prometheus metrics exporter and scraping, see [AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/exporting-and-scraping-prometheus-metrics).
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -9,5 +9,6 @@ children:
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.16'
|
||||
---
|
||||
|
||||
|
||||
@@ -5,6 +5,7 @@ intro: Use the REST API to manage private registry configurations for organizati
|
||||
versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.16'
|
||||
topics:
|
||||
- API
|
||||
autogenerated: rest
|
||||
|
||||
3
data/features/prometheus-metrics-exporter.yml
Normal file
3
data/features/prometheus-metrics-exporter.yml
Normal file
@@ -0,0 +1,3 @@
|
||||
# In GHES 3.16, ability to scrape prometheus-compatible metrics is introduced
|
||||
versions:
|
||||
ghes: '>=3.16'
|
||||
@@ -40,6 +40,12 @@ sections:
|
||||
- |
|
||||
...
|
||||
|
||||
- heading: APIs
|
||||
notes:
|
||||
# LINK TO RELEASE ISSUE
|
||||
- |
|
||||
...
|
||||
|
||||
- heading: Migrations
|
||||
notes:
|
||||
# LINK TO RELEASE ISSUE
|
||||
|
||||
259
data/release-notes/enterprise-server/3-16/0-rc1.yml
Normal file
259
data/release-notes/enterprise-server/3-16/0-rc1.yml
Normal file
@@ -0,0 +1,259 @@
|
||||
date: '2025-02-25'
|
||||
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 [AUTOTITLE](/admin/upgrading-your-instance/preparing-to-upgrade/overview-of-the-upgrade-process).
|
||||
sections:
|
||||
|
||||
features:
|
||||
|
||||
- heading: Instance administration
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/5349
|
||||
- |
|
||||
We have optimized the monitor dashboard to help administrators quickly understand the operational health of the appliance at a glance. The newly added dashboard is concise and has actionable metrics. See [AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/about-the-monitor-dashboards).
|
||||
# https://github.com/github/releases/issues/5348
|
||||
- |
|
||||
GitHub Enterprise Server has Prometheus metrics exporter in the appliance. This was dark-shipped in version 3.12 and the security posture was improved in 3.16. It simplifies the process of setting up an observability and monitoring pipeline that integrates with an external Prometheus installation. Prometheus-compatible metrics can be scraped directly from the appliance. See [AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/exporting-and-scraping-prometheus-metrics).
|
||||
# https://github.com/github/releases/issues/4576
|
||||
- |
|
||||
Organization owners can manage security responsibilities more flexibly with updates to the security manager role. The role can be assigned directly to individual users, in addition to teams, allowing more precise control over security responsibilities. Additionally, security manager assignments are managed under Settings - Organization roles, streamlining role configuration alongside other organizational roles. See [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).
|
||||
|
||||
- heading: Authentication
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/2579
|
||||
- |
|
||||
Enterprise and organization administrators can set limits on token lifetimes for the {% data variables.product.pat_generic_title_case_plural %} (PATs) used against their resources. These policies mandate token rotation on a regular basis and reduce how long a compromised token is good for, while also providing a lever to reduce the use of less-secure PATs in your company. See [New PAT rotation policies preview and optional expiration for fine-grained PATs](https://github.blog/changelog/2024-10-18-new-pat-rotation-policies-preview-and-optional-expiration-for-fine-grained-pats/) on the GitHub blog.
|
||||
|
||||
- heading: Dependabot
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/5434
|
||||
- |
|
||||
Developers using `pnpm` workspaces can ensure more reliable dependency updates with full Dependabot support for `pnpm` workspace catalogs. Dependabot prevents lockfile inconsistencies, avoids broken dependency trees, and improves update reliability in monorepos. See [the GitHub blog post](https://github.blog/changelog/2025-02-04-dependabot-now-supports-pnpm-workspace-catalogs-ga/).
|
||||
# https://github.com/github/releases/issues/4982
|
||||
- |
|
||||
Users can configure Dependabot to create pull requests to keep their repositories up to date with the .NET SDK latest version. When a new version is detected, Dependabot creates a pull request to update the `global.json` file to the new version. See [AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates) and [AUTOTITLE](/code-security/dependabot/working-with-dependabot/dependabot-options-reference#package-ecosystem-).
|
||||
|
||||
- heading: Security overview
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/3926
|
||||
- |
|
||||
On the security overview dashboard, users can find a SAST vulnerabilities summary table that highlights the top 10 CodeQL and third-party open alerts by count, grouped by vulnerability type. This table helps teams prioritize remediation by showing the most widespread vulnerabilities across their codebase. The table is available for both organizations and enterprises in the Detection view. See [AUTOTITLE](/code-security/security-overview/viewing-security-insights).
|
||||
# https://github.com/github/releases/issues/3956
|
||||
- |
|
||||
On the security overview dashboard, users can view Prevention metrics alongside Detection and Remediation metrics at both the organization and enterprise levels. See [the GitHub blog post](https://github.blog/changelog/2024-09-19-enhanced-security-overview-dashboard-detection-remediation-and-prevention-at-the-forefront/).
|
||||
# https://github.com/github/releases/issues/3955
|
||||
- |
|
||||
Users can export CSV data from the "CodeQL pull request alerts" view for an organization. This expansion of the data you can export from security overview makes it easier for you to integrate the data with external systems, craft custom reports, and archive security information. See [AUTOTITLE](/code-security/security-overview/viewing-metrics-for-pull-request-alerts).
|
||||
# https://github.com/github/releases/issues/5032
|
||||
- |
|
||||
On the security overview dashboard, accessibility enhancements improve how users interact with and understand code security insights. Updates include enhanced color contrast, full keyboard navigation, and better screen reader support, making security data more accessible to all users. See [Accessibility improvements for security overview](https://github.blog/changelog/2024-11-20-accessibility-improvements-for-security-overview/) on the GitHub blog.
|
||||
|
||||
- heading: GitHub Actions
|
||||
notes:
|
||||
# Required Actions Runner version
|
||||
- |
|
||||
{% data reusables.actions.actions-runner-release-note %}
|
||||
# https://github.com/github/releases/issues/4360
|
||||
- |
|
||||
Users can see job level annotations above the GitHub Actions log view, improving the discoverability of annotations.
|
||||
# https://github.com/github/releases/issues/4225
|
||||
- |
|
||||
Users can control where CodeQL security analysis runs by specifying any custom label for self-hosted runners in code scanning's default setup. This update removes the previous restriction requiring the `code-scanning` label, allowing analysis to run on the desired machine(s). See [Improved support for labeled Actions runners in CodeQL code scanning](https://github.blog/changelog/2024-12-03-improved-support-for-labeled-actions-runners-in-codeql-code-scanning/) on the GitHub blog.
|
||||
# https://github.com/github/releases/issues/4269
|
||||
- |
|
||||
The CI/CD Admin role is a pre-defined organization role. Organization owners and teams can delegate comprehensive CI/CD management to individuals without the need to maintain a custom role. See [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#about-pre-defined-organization-roles).
|
||||
# https://github.com/github/releases/issues/4309
|
||||
- |
|
||||
Enterprise administrators can authenticate with region-specific OIDC endpoints for improved compliance and performance.
|
||||
|
||||
|
||||
- heading: GitHub Apps
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/4900
|
||||
- |
|
||||
GitHub App developers can improve security with a 25-key limit per app, encouraging safer key management practices. Apps exceeding the limit must delete excess keys before adding new ones. Additionally, scoped tokens can access more repositories. See [AUTOTITLE](/apps/creating-github-apps/authenticating-with-a-github-app/managing-private-keys-for-github-apps).
|
||||
# https://github.com/github/releases/issues/4342
|
||||
- |
|
||||
Enterprise owners can securely manage and share GitHub Apps across all organizations within their enterprise by creating enterprise-owned GitHub Apps. This eliminates the need to duplicate apps or make them public, reducing management overhead while improving security and centralization. See [AUTOTITLE](/admin/managing-your-enterprise-account/creating-github-apps-for-your-enterprise).
|
||||
|
||||
- heading: Repositories
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/4530
|
||||
- |
|
||||
Enterprise and organization administrators can configure policies to restrict the usage of deploy keys across all the repositories of their organizations, giving them more control and greater security over their deploy keys. See [AUTOTITLE](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization#enforcing-a-maximum-lifetime-policy-for-personal-access-tokens).
|
||||
# https://github.com/github/releases/issues/4668
|
||||
- |
|
||||
Enterprise owners are a bypass role in rulesets, which will allow further restrictions in rules bypassing.
|
||||
# https://github.com/github/releases/issues/4671
|
||||
- |
|
||||
Custom repository properties have an “additional options” section that administrators can use to easily manage properties.
|
||||
# https://github.com/github/releases/issues/4600
|
||||
- |
|
||||
Organization rulesets using custom properties include a link to the exact list of repositories targeted.
|
||||
# https://github.com/github/releases/issues/4263
|
||||
- |
|
||||
Organization owners can allow users to set custom properties during repository creation. This ensures appropriate rules are enforced from the moment of creation and improves discoverability of new repositories. See [the GitHub blog post](https://github.blog/changelog/2024-09-10-push-rules-are-now-generally-available-and-updates-to-custom-properties/#custom-properties).
|
||||
|
||||
- heading: Security advisories
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/3949
|
||||
- |
|
||||
Users who report security advisories can use the new CVSS 4.0 schema to calculate a base vulnerability score. See [AUTOTITLE](/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-the-github-advisory-database#about-cvss-levels).
|
||||
# https://github.com/github/releases/issues/4483
|
||||
- |
|
||||
In the GitHub Advisory Database, users have access to an estimated probability that a vulnerability will be exploited over the next 30 days, calculated by the FIRST organization. This Exploit Prediction Scoring System (EPSS) score makes it easier for you to compare the risks of different vulnerabilities to your organization. See [AUTOTITLE](/code-security/security-advisories/working-with-global-security-advisories-from-the-github-advisory-database/about-the-github-advisory-database#about-epss-scores).
|
||||
|
||||
- heading: Code scanning
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/4501
|
||||
- |
|
||||
Advanced setup for CodeQL code scanning supports using an actions dependency cache instead of downloading dependencies from registries in every run. Users should update their workflows to use a dependency cache if access to registries is unreliable or slow. Using a dependency cache reduces the risk of losing alerts when third-party registries don't work well and may produce a small performance improvement. See [AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages#about-dependency-caching-for-codeql).
|
||||
# https://github.com/github/releases/issues/4628
|
||||
- |
|
||||
The CodeQL tools are available as a Zstandard archive with faster download and decompression times compared with the previous Gzipped archive.
|
||||
|
||||
* The time taken to set up CodeQL analysis is reduced for default and advanced setup. No action is required by users of default and advanced setup to use the Zstandard archive, as the CodeQL action will automatically download the new archive.
|
||||
* People who use the CodeQL CLI can directly update their processes to download the new Zstandard archive. See [AUTOTITLE](/code-security/codeql-cli/getting-started-with-the-codeql-cli/setting-up-the-codeql-cli#1-download-the-codeql-cli-tar-archive).
|
||||
|
||||
- heading: Secret scanning
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/4126
|
||||
# https://github.com/github/releases/issues/4658
|
||||
# https://github.com/github/releases/issues/4629
|
||||
# https://github.com/github/releases/issues/4596
|
||||
# https://github.com/github/releases/issues/4595
|
||||
# https://github.com/github/releases/issues/4896
|
||||
- |
|
||||
Repository administrators, organization owners, and security managers can specify which teams or roles have the ability to bypass push protection. These controls introduce a review and approval cycle for pushes containing secrets from all other contributors. This functionality is generally available and includes the following improvements over the preview:
|
||||
* Organization owners and security managers can define different groups of bypass reviewers for groups of repositories using security configurations. See [AUTOTITLE](/code-security/securing-your-organization/enabling-security-features-in-your-organization/creating-a-custom-security-configuration).
|
||||
* When defining bypass reviewers, organization owners and security managers have the flexibility of using a fine-grained permission, in addition to the existing role and team options. See [AUTOTITLE](/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/enabling-delegated-bypass-for-push-protection#using-fine-grained-permissions-to-control-who-can-review-and-manage-bypass-requests).
|
||||
* For blocked secrets, bypass reviewers see the branch and file path of the secret which makes it easier to triage bypass requests effectively. See [AUTOTITLE](/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/managing-requests-to-bypass-push-protection).
|
||||
* Users of the REST API, webhooks, and audit logs have access to additional fields which record details for approved bypass requests resulting in secret scanning alerts. See [Push protection bypass request details are included in the REST API, webhooks, and audit logs for secret scanning alerts](https://github.blog/changelog/2024-11-12-push-protection-bypass-request-details-are-included-in-the-rest-api-webhooks-and-audit-logs-for-secret-scanning-alerts/) on the GitHub blog.
|
||||
* Reviewers can add comments to push protection bypass requests in secret scanning. These comments help provide context, explaining the reasoning behind approving or denying a request. Requesters gain clarity on why their request was denied, and other reviewers can better understand why a request was approved or denied.
|
||||
* Secret scanning supports delegated bypass controls for repository file uploads from the browser. When enabled, users without bypass permissions must submit a request to approved reviewers before uploading a file containing a detected secret, reducing the risk of accidental exposure. See [AUTOTITLE](/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection#about-delegated-bypass-for-push-protection).
|
||||
# https://github.com/github/releases/issues/4261
|
||||
# https://github.com/github/releases/issues/4597
|
||||
- |
|
||||
Automatic detection of non-provider patterns that help you uncover secrets outside of patterns tied to specific token issuers, like HTTP authentication headers, connection strings, and private keys, is generally available. This release includes the following improvement over the preview:
|
||||
* Users can find security alerts from non-provider patterns on the "Experimental" view of the repository "Secret scanning alerts" page for a repository, and in the security overview for an organization. The new name for the view more clearly communicates the status of the alerts than the old name of "Other".
|
||||
# https://github.com/github/releases/issues/4842
|
||||
- |
|
||||
Users who reopen a secret scanning alert manually have the option to add a comment explaining why the alert needs to be reopened. Any comments added will be visible in the alert UI, REST API, and webhooks, in the same way as for comments on dismissing an alert.
|
||||
# https://github.com/github/releases/issues/4708
|
||||
- |
|
||||
Users can use a new REST API endpoint to report on the scanning history for a repository which is useful for auditing scans and also for troubleshooting. See [Access a repository’s secret scanning scan history with the REST API](https://github.blog/changelog/2024-11-27-access-a-repositorys-secret-scanning-scan-history-with-the-rest-api/) on the GitHub blog.
|
||||
|
||||
- heading: Code security
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/4288
|
||||
- |
|
||||
Enterprise owners can simplify and standardize the rollout of GitHub security products by creating security configurations at the enterprise-level. An enterprise configuration can be applied to repositories at the enterprise or the organization level. This gives you the option to enforce security features enterprise-wide, or to define configurations centrally but apply them locally using organization-level filtering to define a group of repositories. See [Code security configurations now available at the enterprise level](https://github.blog/changelog/2024-12-12-code-security-configurations-now-available-at-the-enterprise-level/) on the GitHub blog.
|
||||
# https://github.com/github/releases/issues/4289
|
||||
- |
|
||||
Organization owners and security managers can apply security configurations to archived repositories. This makes it simpler to roll out configurations without having to filter for archived repositories, and ensures features like Dependabot, code scanning, and secret scanning are automatically reapplied if a repository is unarchived. In addition, secret scanning runs on all repositories, including archived repositories, so if you add a new custom pattern, archived repositories will be scanned for matches. See [Code security configurations now support archived repositories](https://github.blog/changelog/2024-10-03-code-security-configurations-now-support-archived-repositories/) on the GitHub blog.
|
||||
# https://github.com/github/releases/issues/4636
|
||||
- |
|
||||
Organization owners and security managers with GitHub Advanced Security enabled have extra filtering options so they can select repositories based on the enablement or disablement of code security features. See [New advanced filters for code security configurations](https://github.blog/changelog/2024-09-18-new-advanced-filters-for-code-security-configurations/) on the GitHub blog.
|
||||
|
||||
- heading: Monitoring
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/5349
|
||||
- |
|
||||
Enterprise administrators can better monitor the health of the appliance with optimized dashboards that provide concise, actionable metrics. See [AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/about-the-monitor-dashboards).
|
||||
|
||||
- heading: Issues
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/4033
|
||||
# https://github.com/github/releases/issues/3121
|
||||
- |
|
||||
Issues and projects feature highly-requested enhancements including sub-issues, issue types, and advanced search for issues. These feature enhancements make it easy to break down work, visualize progress, categorize and find just the right issue in GitHub. See the [GitHub blog post](https://github.blog/changelog/2024-10-01-evolving-github-issues-public-beta/).
|
||||
|
||||
- heading: GitHub Mobile
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/4456
|
||||
- |
|
||||
GitHub Mobile users can stay focused on important updates with Focused Notifications. This feature prioritizes notifications from the past 30 days, including items they've authored, direct mentions, and assigned tasks, helping reduce noise and improve productivity.
|
||||
|
||||
security_fixes:
|
||||
# https://github.com/github/releases/issues/5415
|
||||
- |
|
||||
**HIGH**: An attacker could access environment variables in the debug artifacts uploaded by the CodeQL action after a failed code scanning workflow run. This includes any secrets that were exposed to the workflow as environment variables. The attacker requires read access to the repository to access the debug artifact. Users who do not have debug logging enabled are unaffected. The impact to GitHub Enterprise Server users is limited to internal actors. To mitigate this issue, GitHub no longer logs the complete environment by default. GitHub has requested [CVE-2025-24362](https://www.cve.org/CVERecord?id=CVE-2025-24362) for this vulnerability, which was reported via the [GitHub Bug Bounty program](https://bounty.github.com/).
|
||||
|
||||
changes:
|
||||
- |
|
||||
The 400GB root disk requirement introduced in [Enterprise Server 3.15.0](/enterprise-server@3.15/admin/release-notes#3.15.0-features) has been reverted in 3.15.2. The 400GB root disk size is no longer a requirement for new GHES installations and upgrades. Customers on standalone or standalone HA topologies are still recommended to upgrade their root disk size to 400GB.
|
||||
# https://github.com/github/releases/issues/4336
|
||||
- |
|
||||
`ghe-config-apply` applies configuration changes conditionally to the relevant, targeted and specific migrations only. As a result, you can expect less downtime and fewer errors while running `ghe-config-apply`. You can still choose to run `ghe-config-apply` unconditionally using this command: `ghe-config-apply -f`.
|
||||
# https://github.com/github/releases/issues/4913
|
||||
- |
|
||||
When an enterprise requires two-factor authentication (2FA), members who do not use 2FA still retain membership even without 2FA, including occupying seats in the enterprise and organizations. However, these users won't be able to access the enterprise resources until they enable 2FA on their account. See [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization).
|
||||
# https://github.com/github/releases/issues/4676
|
||||
- |
|
||||
The Debian and RedHat releases have been signed with a new GPG key. If you installed `gh` via our official package repositories, please update your keyring to the new key to continue verifying GitHub CLI releases. See the [GitHub blog post](https://github.blog/changelog/2024-09-11-github-cli-renews-gpg-signing-key-for-linux-packages/).
|
||||
# https://github.com/github/releases/issues/5415
|
||||
- |
|
||||
The CodeQL Action has been updated to v3.28.6 to enable uploading artifacts in debug mode without logging the complete environment when running CodeQL CLI v2.20.3+.
|
||||
|
||||
known_issues:
|
||||
- |
|
||||
**Note:** This list is not complete. Any new known issues that are identified for the 3.16 release will be added between now and the general availability release.
|
||||
- |
|
||||
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. 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.large-adoc-files-issue %}
|
||||
- |
|
||||
Admin stats REST API endpoints may timeout on appliances with many users or repositories. Retrying the request until data is returned is advised.
|
||||
- |
|
||||
When following the steps for [Replacing the primary MySQL node](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/replacing-a-cluster-node#replacing-the-primary-mysql-node), step 14 (running `ghe-cluster-config-apply`) might fail with errors. If this occurs, re-running `ghe-cluster-config-apply` is expected to succeed.
|
||||
- |
|
||||
Running a config apply as part of the steps for [Replacing a node in an emergency](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/replacing-a-cluster-node#replacing-a-node-in-an-emergency) may fail with errors if the node being replaced is still reachable. If this occurs, shutdown the node and repeat the steps.
|
||||
- |
|
||||
When restoring data originally backed up from an appliance with version 3.13 or greater, the Elasticsearch indices must be reindexed before the data will display. This happens via a nightly scheduled job. It can also be forced by running `/usr/local/share/enterprise/ghe-es-search-repair`.
|
||||
- |
|
||||
An organization-level code scanning configuration page displays on instances that do not use GitHub Advanced Security or code scanning.
|
||||
- |
|
||||
When initializing a new GHES cluster, nodes with the `consul-server` role should be added to the cluster before adding additional nodes. Adding all nodes simultaneously creates a race condition between nomad server registration and nomad client registration.
|
||||
- |
|
||||
Admins setting up cluster high availability (HA) may encounter a spokes error when running `ghe-cluster-repl-status` if a new organization and repositories are created before using the ghe-cluster-repl-bootstrap command. To avoid this issue, complete the cluster HA setup with `ghe-cluster-repl-bootstrap` before creating new organizations and repositories.
|
||||
- |
|
||||
Customers upgrading from 3.11.x or 3.12.x may experience a bug with the feature "Automatic update checks", which fills the root disk with logs causing a system degradation. To prevent this, turn off the feature "[Enable automatic update check](/admin/upgrading-your-instance/preparing-to-upgrade/enabling-automatic-update-checks#enabling-automatic-update-checks)" in the management console.
|
||||
- |
|
||||
In a cluster, the host running restore requires access the storage nodes via their private IPs.
|
||||
- |
|
||||
Commenting on an issue via email is not reflected on the issue in Azure.
|
||||
- |
|
||||
After a restore, existing outside collaborators cannot be added to repositories in a new organization. This issue can be resolved by running `/usr/local/share/enterprise/ghe-es-search-repair` on the appliance.
|
||||
- |
|
||||
After a geo-replica is promoted to primary by running `ghe-repl-promote`, the actions workflow of a repository does not have any suggested workflows.
|
||||
|
||||
closing_down:
|
||||
# https://github.com/github/releases/issues/4683
|
||||
- |
|
||||
As of November 6, 2024, Dependabot no longer supports Composer version 1, which has reached its end-of-life. If you continue to use Composer version 1, Dependabot will be unable to create pull requests to update your dependencies. If this affects you, we recommend updating to a supported release of Composer. As of October 2024, the newest supported version of Composer is 2.8, and the long-term supported version is 2.2. View [Composer's official documentation](https://getcomposer.org/download/) for more information about supported releases.
|
||||
|
||||
retired:
|
||||
- |
|
||||
Team discussions have been removed from GitHub Enterprise Server. The sunset of this feature was announced in 2023. See the [GitHub Blog post](https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/).
|
||||
# https://github.com/github/releases/issues/4964
|
||||
- |
|
||||
In GitHub Enterprise Server 3.16, the `/explore` functionality, including the Activity and Trending pages, is removed.
|
||||
# https://github.com/github/releases/issues/4380
|
||||
- |
|
||||
GitHub no longer supports .NET 6 in GitHub Enterprise Server 3.16 and later.
|
||||
# https://github.com/github/releases/issues/4535
|
||||
- |
|
||||
As of October 15th, 2024, you will no longer be able to enable or disable GitHub security features for repositories from the organization-level security coverage view. This feature has been deprecated and replaced with code security configurations for managing these settings. See the [GitHub blog post](https://github.blog/changelog/2024-10-17-new-code-security-configurations-let-you-set-security-features-at-the-organization-level/).
|
||||
@@ -1,5 +1,4 @@
|
||||
{% ifversion ghec %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
>[!NOTE] Some features enabled in {% data variables.product.prodname_security_configurations %} may require Actions minutes to work. {% data variables.product.prodname_dotcom %} will let you know if that's the case when you apply the configuration to a repository. For more information about billing for {% data variables.product.prodname_actions %}, see [AUTOTITLE](/billing/managing-billing-for-github-actions/about-billing-for-github-actions).
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -147,7 +147,7 @@ prodname_unfurls: 'Content Attachments'
|
||||
prodname_actions: 'GitHub Actions'
|
||||
prodname_actions_runner_controller: 'Actions Runner Controller'
|
||||
runner_required_version: >-
|
||||
{% ifversion ghes < 3.13 %}2.311.0{% elsif ghes < 3.14 %}2.314.1{% elsif ghes < 3.15 %}2.317.0{% elsif ghes < 3.16 %}2.319.1{% endif %}
|
||||
{% ifversion ghes < 3.13 %}2.311.0{% elsif ghes < 3.14 %}2.314.1{% elsif ghes < 3.15 %}2.317.0{% elsif ghes < 3.16 %}2.319.1{% elsif ghes < 3.17 %}2.321.0{% endif %}
|
||||
|
||||
# GitHub Debug
|
||||
prodname_debug: 'GitHub Debug'
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
4548
src/github-apps/data/ghes-3.16-2022-11-28/fine-grained-pat.json
Normal file
4548
src/github-apps/data/ghes-3.16-2022-11-28/fine-grained-pat.json
Normal file
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
4180
src/github-apps/data/ghes-3.16-2022-11-28/server-to-server-rest.json
Normal file
4180
src/github-apps/data/ghes-3.16-2022-11-28/server-to-server-rest.json
Normal file
File diff suppressed because it is too large
Load Diff
4548
src/github-apps/data/ghes-3.16-2022-11-28/user-to-server-rest.json
Normal file
4548
src/github-apps/data/ghes-3.16-2022-11-28/user-to-server-rest.json
Normal file
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,546 @@
|
||||
---
|
||||
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: TopicSuggestionDeclineReason.NOT_RELEVANT
|
||||
description: '`NOT_RELEVANT` will be removed.'
|
||||
reason: Suggested topics are no longer supported
|
||||
date: '2024-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: calvinchilds
|
||||
- location: TopicSuggestionDeclineReason.PERSONAL_PREFERENCE
|
||||
description: '`PERSONAL_PREFERENCE` will be removed.'
|
||||
reason: Suggested topics are no longer supported
|
||||
date: '2024-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: calvinchilds
|
||||
- location: TopicSuggestionDeclineReason.TOO_GENERAL
|
||||
description: '`TOO_GENERAL` will be removed.'
|
||||
reason: Suggested topics are no longer supported
|
||||
date: '2024-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: calvinchilds
|
||||
- location: TopicSuggestionDeclineReason.TOO_SPECIFIC
|
||||
description: '`TOO_SPECIFIC` will be removed.'
|
||||
reason: Suggested topics are no longer supported
|
||||
date: '2024-04-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: calvinchilds
|
||||
- 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: OrganizationInvitation.inviter
|
||||
description: '`inviter` will be removed. `inviter` will be replaced by `inviterActor`.'
|
||||
reason: '`inviter` will be removed.'
|
||||
date: '2024-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: jdennes
|
||||
- location: PullRequest.databaseId
|
||||
description: '`databaseId` will be removed. Use `fullDatabaseId` instead.'
|
||||
reason:
|
||||
'`databaseId` will be removed because it does not support 64-bit signed
|
||||
integer identifiers.'
|
||||
date: '2024-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: JanKoszewski
|
||||
- location: PullRequestReview.databaseId
|
||||
description: '`databaseId` will be removed. Use `fullDatabaseId` instead.'
|
||||
reason:
|
||||
'`databaseId` will be removed because it does not support 64-bit signed
|
||||
integer identifiers.'
|
||||
date: '2024-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: JanKoszewski
|
||||
- location: PullRequestReviewComment.databaseId
|
||||
description: '`databaseId` will be removed. Use `fullDatabaseId` instead.'
|
||||
reason:
|
||||
'`databaseId` will be removed because it does not support 64-bit signed
|
||||
integer identifiers.'
|
||||
date: '2024-07-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: JanKoszewski
|
||||
- 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
|
||||
- location: Workflow.hasWorkflowDispatchTrigger
|
||||
description:
|
||||
'`hasWorkflowDispatchTrigger` will be removed. Use `has_workflow_dispatch_trigger_for_branch(branch_ref)`
|
||||
instead.'
|
||||
reason:
|
||||
"`has_workflow_dispatch_trigger` is being removed because it can be misleading
|
||||
and only checks a repository's default branch"
|
||||
date: '2024-10-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: stevepopovich
|
||||
- location: AddMobileDevicePublicKeyPayload.expiresAt
|
||||
description:
|
||||
'`expiresAt` will be removed. Do not rely on this field, it is currently
|
||||
set to a date far in the future if a device key is expirationless'
|
||||
reason: We are deprecating expirations for mobile device keys used in mobile 2FA
|
||||
date: '2025-01-01T00:00:00+00:00'
|
||||
criticality: breaking
|
||||
owner: chriskirkland
|
||||
1
src/graphql/data/ghes-3.16/previews.json
Normal file
1
src/graphql/data/ghes-3.16/previews.json
Normal file
@@ -0,0 +1 @@
|
||||
[]
|
||||
57264
src/graphql/data/ghes-3.16/schema.docs-enterprise.graphql
Normal file
57264
src/graphql/data/ghes-3.16/schema.docs-enterprise.graphql
Normal file
File diff suppressed because it is too large
Load Diff
96262
src/graphql/data/ghes-3.16/schema.json
Normal file
96262
src/graphql/data/ghes-3.16/schema.json
Normal file
File diff suppressed because it is too large
Load Diff
600
src/graphql/data/ghes-3.16/upcoming-changes.json
Normal file
600
src/graphql/data/ghes-3.16/upcoming-changes.json
Normal file
@@ -0,0 +1,600 @@
|
||||
{
|
||||
"2025-01-01": [
|
||||
{
|
||||
"location": "AddMobileDevicePublicKeyPayload.expiresAt",
|
||||
"description": "<p><code>expiresAt</code> will be removed. Do not rely on this field, it is currently set to a date far in the future if a device key is expirationless</p>",
|
||||
"reason": "<p>We are deprecating expirations for mobile device keys used in mobile 2FA</p>",
|
||||
"date": "2025-01-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "chriskirkland"
|
||||
}
|
||||
],
|
||||
"2024-10-01": [
|
||||
{
|
||||
"location": "Workflow.hasWorkflowDispatchTrigger",
|
||||
"description": "<p><code>hasWorkflowDispatchTrigger</code> will be removed. Use <code>has_workflow_dispatch_trigger_for_branch(branch_ref)</code> instead.</p>",
|
||||
"reason": "<p><code>has_workflow_dispatch_trigger</code> is being removed because it can be misleading and only checks a repository's default branch</p>",
|
||||
"date": "2024-10-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "stevepopovich"
|
||||
}
|
||||
],
|
||||
"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": "PullRequestReviewComment.databaseId",
|
||||
"description": "<p><code>databaseId</code> will be removed. Use <code>fullDatabaseId</code> instead.</p>",
|
||||
"reason": "<p><code>databaseId</code> will be removed because it does not support 64-bit signed integer identifiers.</p>",
|
||||
"date": "2024-07-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "JanKoszewski"
|
||||
},
|
||||
{
|
||||
"location": "PullRequestReview.databaseId",
|
||||
"description": "<p><code>databaseId</code> will be removed. Use <code>fullDatabaseId</code> instead.</p>",
|
||||
"reason": "<p><code>databaseId</code> will be removed because it does not support 64-bit signed integer identifiers.</p>",
|
||||
"date": "2024-07-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "JanKoszewski"
|
||||
},
|
||||
{
|
||||
"location": "PullRequest.databaseId",
|
||||
"description": "<p><code>databaseId</code> will be removed. Use <code>fullDatabaseId</code> instead.</p>",
|
||||
"reason": "<p><code>databaseId</code> will be removed because it does not support 64-bit signed integer identifiers.</p>",
|
||||
"date": "2024-07-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "JanKoszewski"
|
||||
},
|
||||
{
|
||||
"location": "OrganizationInvitation.inviter",
|
||||
"description": "<p><code>inviter</code> will be removed. <code>inviter</code> will be replaced by <code>inviterActor</code>.</p>",
|
||||
"reason": "<p><code>inviter</code> will be removed.</p>",
|
||||
"date": "2024-07-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "jdennes"
|
||||
},
|
||||
{
|
||||
"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"
|
||||
}
|
||||
],
|
||||
"2024-04-01": [
|
||||
{
|
||||
"location": "TopicSuggestionDeclineReason.TOO_SPECIFIC",
|
||||
"description": "<p><code>TOO_SPECIFIC</code> will be removed.</p>",
|
||||
"reason": "<p>Suggested topics are no longer supported</p>",
|
||||
"date": "2024-04-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "calvinchilds"
|
||||
},
|
||||
{
|
||||
"location": "TopicSuggestionDeclineReason.TOO_GENERAL",
|
||||
"description": "<p><code>TOO_GENERAL</code> will be removed.</p>",
|
||||
"reason": "<p>Suggested topics are no longer supported</p>",
|
||||
"date": "2024-04-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "calvinchilds"
|
||||
},
|
||||
{
|
||||
"location": "TopicSuggestionDeclineReason.PERSONAL_PREFERENCE",
|
||||
"description": "<p><code>PERSONAL_PREFERENCE</code> will be removed.</p>",
|
||||
"reason": "<p>Suggested topics are no longer supported</p>",
|
||||
"date": "2024-04-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "calvinchilds"
|
||||
},
|
||||
{
|
||||
"location": "TopicSuggestionDeclineReason.NOT_RELEVANT",
|
||||
"description": "<p><code>NOT_RELEVANT</code> will be removed.</p>",
|
||||
"reason": "<p>Suggested topics are no longer supported</p>",
|
||||
"date": "2024-04-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "calvinchilds"
|
||||
}
|
||||
],
|
||||
"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"
|
||||
}
|
||||
]
|
||||
}
|
||||
551074
src/rest/data/ghes-3.16-2022-11-28/schema.json
Normal file
551074
src/rest/data/ghes-3.16-2022-11-28/schema.json
Normal file
File diff suppressed because one or more lines are too long
@@ -17,6 +17,9 @@
|
||||
],
|
||||
"ghes-3.15": [
|
||||
"2022-11-28"
|
||||
],
|
||||
"ghes-3.16": [
|
||||
"2022-11-28"
|
||||
]
|
||||
},
|
||||
"versionMapping": {
|
||||
|
||||
@@ -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.16'
|
||||
export const nextNext = '3.17'
|
||||
export const next = '3.17'
|
||||
export const nextNext = '3.18'
|
||||
|
||||
export const supported = ['3.15', '3.14', '3.13', '3.12']
|
||||
export const supported = ['3.16', '3.15', '3.14', '3.13', '3.12']
|
||||
|
||||
// Edit this to `null` when it's no longer the release candidate
|
||||
export const releaseCandidate = null
|
||||
export const releaseCandidate = '3.16'
|
||||
|
||||
// Ensure that:
|
||||
// "next" is ahead of "latest" by one minor or major release.
|
||||
|
||||
221328
src/webhooks/data/ghes-3.16/schema.json
Normal file
221328
src/webhooks/data/ghes-3.16/schema.json
Normal file
File diff suppressed because it is too large
Load Diff
Reference in New Issue
Block a user