зеркало из https://github.com/github/docs.git
GitHub Enterprise Server 3.11 release candidate (#44684)
Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> Co-authored-by: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com> Co-authored-by: docs-bot <77750099+docs-bot@users.noreply.github.com> Co-authored-by: Vanessa <vgrl@github.com>
This commit is contained in:
Isaac Brown
GitHub
Родитель
3f55bf914f
Коммит
352440fc17
|
|
@ -0,0 +1,112 @@
|
|||
Category,Old Attribute,New Attribute
|
||||
Memex,queue,gh.job.queue
|
||||
Memex,status,gh.memex.automation.status
|
||||
Memex,topic,messaging.kafka.source.topic
|
||||
Memex,partition,messaging.kafka.source.partition
|
||||
Memex,schema,messaging.kafka.message.schema
|
||||
Memex,offset,messaging.kafka.message.offset
|
||||
Memex,timestamp,messaging.kafka.message.timestamp
|
||||
Memex,item_ids,gh.memex.unauthorized_item_ids
|
||||
Authzd,authzd_request,gh.authzd.request.attributes
|
||||
Authzd,authzd.request,gh.authzd.request.attributes
|
||||
Authzd,authzd_response,gh.authzd.decisions
|
||||
Authzd,authzd.response,gh.authzd.decisions
|
||||
Authzd,authzd.rpc,gh.authzd.rpc
|
||||
Authzd,gh.authzd.enumerator.request.size,gh.authzd.enumerator.response.size
|
||||
Dependency Graph,job_timeout,gh.job.timeout
|
||||
Dependency Graph,push_id,gh.push.id
|
||||
Dependency Graph,ref,gh.commit.ref
|
||||
Dependency Graph,commit_sha,gh.commit.oid
|
||||
Dependency Graph,repo_count,gh.dependency_graph.manifest_paths_count
|
||||
Dependency Graph,max_manifest_files,gh.dependency_graph.max_manifest_files
|
||||
Dependency Graph,push_count,gh.dependency_graph.changed_manifest.count
|
||||
Dependency Graph,base,gh.comparison.base_rev
|
||||
Dependency Graph,head,gh.comparison.head_rev
|
||||
Driftwood,deployed_to,gh.driftwood.deployed_to
|
||||
Driftwood,release,gh.driftwood.release
|
||||
Driftwood,ref,gh.driftwood.ref
|
||||
Driftwood,service,gh.driftwood.service
|
||||
Driftwood,exception_id,gh.driftwood.exception_id
|
||||
Registry,ecosystem,gh.registry.ecosystem
|
||||
Registry,v2_enabled,gh.registry.v2_enabled
|
||||
Registry,display_login,gh.registry.display_login
|
||||
Registry,user_id,gh.registry.owner_id
|
||||
Registry,namespace,gh.registry.namespace
|
||||
Registry,namespace,gh.registry.user_name
|
||||
Registry,version,gh.registry.version
|
||||
Registry,no_versions,gh.registry.no_versions
|
||||
Registry,latest_version_id,gh.registry.latest_version_id
|
||||
Registry,force,gh.registry.force
|
||||
Registry,retry_failed,gh.registry.retry_failed
|
||||
Registry,package_type,gh.registry.package_type
|
||||
Registry,N/A,gh.registry.pkg_count
|
||||
Registry,N/A,gh.registry.namespace_count
|
||||
Registry,N/A,gh.registry.unmigrated_package_count
|
||||
Registry,repo,gh.registry.repository_name
|
||||
Packages,name,gh.packages.user_name
|
||||
Packages,repo,gh.packages.repository_name
|
||||
Packages,actions_usage,gh.packages.actions_usage
|
||||
Packages,combined_usage,gh.packages.combined_usage
|
||||
Packages,known_packages_usage,gh.packages.known_packages_usage
|
||||
Packages,overcharged_usage,gh.packages.overcharged_usage
|
||||
Packages,billing_difference,gh.packages.billing_difference
|
||||
Container Registry,owner,gh.container-registry.owner_name
|
||||
Container Registry,repository,gh.container-registry.repository_name
|
||||
Container Registry,combined_usage,gh.container-registry.combined_usage
|
||||
Container Registry,actions_usage,gh.container-registry.actions_usage
|
||||
Container Registry,non_docker_usage,gh.container-registry.non_docker_usage
|
||||
Container Registry,docker_usage,gh.container-registry.docker_usage
|
||||
Container Registry,size,gh.container-registry.size
|
||||
Registry,package_id,gh.registry.package_id
|
||||
Registry,unmigrated_count,gh.registry.unmigrated_count
|
||||
Registry,failed_count,gh.registry.failed_count
|
||||
Registry,unmigrated_ver_count,gh.registry.unmigrated_ver_count
|
||||
Registry,failed_ver_count,gh.registry.failed_ver_count
|
||||
Registry,id,gh.registry.migration_run_id
|
||||
Registry,success_pkg_count,gh.registry.success_pkg_count
|
||||
Registry,failed_pkg_count,gh.registry.failed_pkg_count
|
||||
Registry,success_org_count,gh.registry.success_org_count
|
||||
Registry,failed_org_count,gh.registry.failed_org_count
|
||||
Registry,migrated_pkg_count,gh.registry.migrated_pkg_count
|
||||
Registry,total_org_count,gh.registry.total_org_count
|
||||
Registry,total_pkg_count,gh.registry.total_pkg_count
|
||||
Registry,enqueued_at,gh.registry.job_enqueued_at
|
||||
Registry,is_forced,gh.registry.job_is_forced
|
||||
Registry,is_error_retry,gh.registry.job_is_error_retry
|
||||
Registry,delay_package_migration,gh.registry.job_delay_package_migration
|
||||
Registry,is_first_run,gh.registry.job_is_first_run
|
||||
Registry,offset_id,gh.registry.job_offset_id
|
||||
Registry,progress,gh.registry.job_progress
|
||||
Registry,created_at,gh.registry.created_at
|
||||
Registry,unmigrated_version_count,gh.registry.unmigrated_version_count
|
||||
Registry,owner_ids,gh.registry.unmigrated_owner_ids
|
||||
Registry,ecosystem,gh.registry.package_ecosystem
|
||||
Registry,batch,gh.registry.batch
|
||||
Registry,namespace,gh.registry.package_namespace
|
||||
Registry,N/A,gh.registry.version_name
|
||||
Registry,N/A,gh.registry.retry_count
|
||||
Registry,version_id,gh.registry.version_id
|
||||
Registry,owner,gh.registry.owner_namespace
|
||||
Registry,actor_id,gh.registry.actor_id
|
||||
Registry,version_deleted_name,gh.registry.version_deleted_name
|
||||
Registry,N/A,gh.registry.hydro_message
|
||||
Registry,N/A,gh.registry.hydro_partition
|
||||
Registry,N/A,gh.registry.hydro_offset
|
||||
Registry,user,gh.registry.user
|
||||
Registry,N/A,gh.registry.migrated_package_id
|
||||
Registry,unmigrated_count,gh.registry.unmigrated_count
|
||||
Registry,last_migrated_package_id,gh.registry.last_migrated_package_id
|
||||
Registry,last_migrated_version_id,gh.registry.last_migrated_version_id
|
||||
Registry,value,gh.registry.value
|
||||
AWS Namespace Cleaner,readonly,gh.aws_namespace_cleaner.readonly
|
||||
AWS Namespace Cleaner,namespace,gh.aws_namespace_cleaner.namespace
|
||||
AWS Namespace Cleaner,owner_id,gh.aws_namespace_cleaner.owner_id
|
||||
AWS Namespace Cleaner,batch_size,gh.aws_namespace_cleaner.batch_size
|
||||
AWS Namespace Cleaner,count,gh.aws_namespace_cleaner.count
|
||||
AWS Namespace Cleaner,objects,gh.aws_namespace_cleaner.objects
|
||||
AWS Namespace Cleaner,errors,gh.aws_namespace_cleaner.errors
|
||||
AWS Namespace Cleaner,guid,gh.aws_namespace_cleaner.guid
|
||||
AWS Namespace Cleaner,deleted,gh.aws_namespace_cleaner.deleted
|
||||
Apps,github_app,gh.integration.slug
|
||||
Apps,current_integration,gh.integration.id
|
||||
Apps,current_integration_installation,gh.installation.id
|
||||
|
|
|
@ -0,0 +1,22 @@
|
|||
---
|
||||
title: Administering your instance using the GitHub CLI
|
||||
intro: 'You can adminster your GitHub Enterprise Server instance using the GitHub CLI extension for GHES Manage API.'
|
||||
versions:
|
||||
feature: ghes-manage-api-cli-extension
|
||||
type: how_to
|
||||
topics:
|
||||
- Enterprise
|
||||
- Fundamentals
|
||||
shortTitle: Using the GitHub CLI
|
||||
---
|
||||
## About the `gh es` extension for {% data variables.product.prodname_cli %}
|
||||
|
||||
{% data reusables.cli.about-cli %} For more information about the {% data variables.product.prodname_cli %}, see "[AUTOTITLE](/github-cli/github-cli/about-github-cli)".
|
||||
|
||||
`gh es` is a {% data variables.product.prodname_cli %} extension that allows you to perform administrative tasks on {% data variables.location.product_location %} by using the instance's REST API endpoints. For more information about GitHub CLI extensions, see "[AUTOTITLE](/github-cli/github-cli/using-github-cli-extensions)".
|
||||
|
||||
You can use the `gh es` extension to manage the root site administrator password, configure maintenance mode, view metadata and status information for your instance's nodes, and more. For installation and usage instructions, see the [github/gh-es repository](https://github.com/github/gh-es) on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[AUTOTITLE](/rest/enterprise-admin/manage-ghes)"
|
||||
|
|
@ -42,7 +42,8 @@ $ ghe-announce -d -s MESSAGE
|
|||
> Announcement message set.
|
||||
# Removes a previously set message
|
||||
$ ghe-announce -u
|
||||
> Removed the announcement message, which was user dismissible: MESSAGE
|
||||
> Removed the announcement message, which was user
|
||||
> dismissible: MESSAGE
|
||||
```
|
||||
|
||||
{% endif %}
|
||||
|
|
@ -68,9 +69,11 @@ With this command, you can also pause or resume jobs in the queue.
|
|||
|
||||
```shell
|
||||
$ ghe-aqueduct status
|
||||
# lists queues and the number of currently queued jobs for all queues
|
||||
# lists queues and the number of currently queued jobs
|
||||
# for all queues
|
||||
$ ghe-aqueduct queue_depth --queue QUEUE
|
||||
# lists the number of currently queued jobs for the specified queue
|
||||
# lists the number of currently queued jobs for the
|
||||
# specified queue
|
||||
$ ghe-aqueduct pause --queue QUEUE
|
||||
# pauses the specified queue
|
||||
$ ghe-aqueduct resume --queue QUEUE
|
||||
|
|
@ -115,7 +118,8 @@ With this utility, you can both retrieve and modify the configuration settings o
|
|||
$ ghe-config core.github-hostname
|
||||
# Gets the configuration value of `core.github-hostname`
|
||||
$ ghe-config core.github-hostname URL
|
||||
# Sets the configuration value of `core.github-hostname` to the specified URL
|
||||
# Sets the configuration value of `core.github-hostname`
|
||||
# to the specified URL
|
||||
$ ghe-config -l
|
||||
# Lists all the configuration values
|
||||
```
|
||||
|
|
@ -130,7 +134,8 @@ Allows you to exempt a list of users from REST API rate limits. A hard limit of
|
|||
|
||||
``` shell
|
||||
$ ghe-config app.github.rate-limiting-exempt-users "hubot github-actions[bot]"
|
||||
# Exempts the users hubot and github-actions[bot] from rate limits. Usernames are case-sensitive.
|
||||
# Exempts the users hubot and github-actions[bot] from rate limits.
|
||||
# Usernames are case-sensitive.
|
||||
```
|
||||
|
||||
### ghe-config-apply
|
||||
|
|
@ -632,6 +637,27 @@ ghe-cluster-balance help
|
|||
|
||||
{% endif %}
|
||||
|
||||
### ghe-cluster-maintenance
|
||||
|
||||
With the `ghe-cluster-maintenance` utility, you can set or unset maintenance mode for every node in a cluster.
|
||||
|
||||
```shell
|
||||
$ ghe-cluster-maintenance -h
|
||||
# Shows options
|
||||
$ ghe-cluster-maintenance -q
|
||||
# Queries the current mode
|
||||
$ ghe-cluster-maintenance -s
|
||||
# Sets maintenance mode
|
||||
{%- ifversion custom-maintenance-mode-message %}
|
||||
$ ghe-cluster-maintenance -s "MESSAGE"
|
||||
# Sets maintenance mode with a custom message
|
||||
$ ghe-cluster-maintenance -m "MESSAGE"
|
||||
# Updates the custom message
|
||||
{%- endif %}
|
||||
$ ghe-cluster-maintenance -u
|
||||
# Unsets maintenance mode
|
||||
```
|
||||
|
||||
### ghe-cluster-status
|
||||
|
||||
Check the health of your nodes and services in a cluster deployment of {% data variables.product.prodname_ghe_server %}.
|
||||
|
|
|
|||
|
|
@ -8,6 +8,7 @@ topics:
|
|||
- Enterprise
|
||||
children:
|
||||
- /accessing-the-administrative-shell-ssh
|
||||
- /administering-your-instance-using-the-github-cli
|
||||
- /command-line-utilities
|
||||
shortTitle: Command line
|
||||
---
|
||||
|
|
|
|||
|
|
@ -16,6 +16,8 @@ topics:
|
|||
|
||||
{% data reusables.enterprise_site_admin_settings.management-console-access %} For more information about {% data variables.enterprise.management_console %} access, see "[AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console)."
|
||||
|
||||
{% ifversion ghes-manage-api-cli-extension %}You can also use the `gh es` {% data variables.product.prodname_cli %} extension to manage the root site administrator password, which controls access to the Management Console. For more information, see the [GH ES CLI usage documentation](https://github.com/github/gh-es/blob/main/USAGE.md#gh-es-access-set-password) and "[AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-command-line/administering-your-instance-using-the-github-cli)".{% endif %}
|
||||
|
||||
{% ifversion enterprise-management-console-multi-user-auth %}
|
||||
|
||||
## Types of {% data variables.enterprise.management_console %} accounts
|
||||
|
|
|
|||
|
|
@ -93,30 +93,25 @@ You can schedule maintenance for different times or dates with the {% data varia
|
|||
|
||||
{% endif %}
|
||||
|
||||
## Enabling or disabling maintenance mode for {% data variables.product.prodname_ghe_server %} via the CLI
|
||||
{% ifversion ghes-manage-api-cli-extension %}
|
||||
|
||||
With the `ghe-maintenance` utility, you can set or unset maintenance mode for a single instance of {% data variables.product.prodname_ghe_server %}.
|
||||
## Managing maintenance mode using the {% data variables.product.prodname_cli %}
|
||||
|
||||
```shell
|
||||
$ ghe-maintenance -h
|
||||
# Shows options
|
||||
$ ghe-maintenance -q
|
||||
# Queries the current mode
|
||||
$ ghe-maintenance -s
|
||||
# Sets maintenance mode
|
||||
{%- ifversion custom-maintenance-mode-message %}
|
||||
$ ghe-maintenance -s "MESSAGE"
|
||||
# Sets maintenance mode with a custom message
|
||||
$ ghe-maintenance -m "MESSAGE"
|
||||
# Updates the custom message
|
||||
{%- endif %}
|
||||
$ ghe-maintenance -u
|
||||
# Unsets maintenance mode
|
||||
```
|
||||
You can manage maintenance mode on {% data variables.location.product_location %} using the {% data variables.product.prodname_cli %} `gh es` extension. For more information, see the GH ES CLI usage documentation for [`gh es maintenance set`](https://github.com/github/gh-es/blob/main/USAGE.md#gh-es-maintenance-set) and [`gh es maintenance get`](https://github.com/github/gh-es/blob/main/USAGE.md#gh-es-maintenance-get).
|
||||
|
||||
## Enabling or disabling maintenance mode for all nodes in a cluster via the CLI
|
||||
For more information, see "[AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-command-line/administering-your-instance-using-the-github-cli)".
|
||||
|
||||
With the `ghe-cluster-maintenance` utility, you can set or unset maintenance mode for every node in a cluster.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion custom-maintenance-mode-message %}
|
||||
|
||||
## Managing maintenance mode using SSH
|
||||
|
||||
If you have SSH access, you can use the `ghe-maintenance` command line utility to can set or unset maintenance mode for a {% data variables.product.product_name %} instance with one node, or multiple nodes in a high-availability configuration. For more information, see "[AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-command-line/accessing-the-administrative-shell-ssh)" and "[AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-command-line/command-line-utilities#ghe-maintenance)."
|
||||
|
||||
## Managing maintenance mode for a cluster using SSH
|
||||
|
||||
If you have SSH access to your {% data variables.product.prodname_ghe_server %} instance, you can use the `ghe-cluster-maintenance` command line utility to set or unset maintenance mode for every node in a cluster. For more information, see "[AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-command-line/accessing-the-administrative-shell-ssh)" and "[AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-command-line/command-line-utilities#ghe-cluster-maintenance)."
|
||||
|
||||
```shell
|
||||
$ ghe-cluster-maintenance -h
|
||||
|
|
@ -134,3 +129,5 @@ $ ghe-cluster-maintenance -m "MESSAGE"
|
|||
$ ghe-cluster-maintenance -u
|
||||
# Unsets maintenance mode
|
||||
```
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -47,6 +47,14 @@ admin@ghe-data-node-0:~$ ghe-cluster-status | grep error
|
|||
|
||||
{% endnote %}
|
||||
|
||||
{% ifversion ghes-manage-api-cli-extension %}
|
||||
|
||||
## Monitoring cluster status using the {% data variables.product.prodname_cli %}
|
||||
|
||||
You can use the `gh es` extension for {% data variables.product.prodname_cli %} to check the status of your {% data variables.product.product_name %} cluster. For more information, see the [GH ES CLI usage documentation](https://github.com/github/gh-es/blob/main/USAGE.md#gh-es-cluster-status) and "[AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-command-line/administering-your-instance-using-the-github-cli)".
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Monitoring cluster status with Nagios
|
||||
|
||||
You can configure [Nagios](https://www.nagios.org/) to monitor {% data variables.product.prodname_ghe_server %}. In addition to monitoring basic connectivity to each of the cluster nodes, you can check the cluster status by configuring Nagios to use the `ghe-cluster-status -n` command. This returns output in a format that Nagios understands.
|
||||
|
|
|
|||
|
|
@ -31,6 +31,14 @@ You can also monitor replication status from the overview dashboard on your inst
|
|||
|
||||
`http(s)://HOSTNAME/setup/replication`
|
||||
|
||||
{% ifversion ghes-manage-api-cli-extension %}
|
||||
|
||||
## Monitoring replication using the {% data variables.product.prodname_cli %}
|
||||
|
||||
You can monitor replication status on your instance using the `gh es` extension for {% data variables.product.prodname_cli %}. For more information, see the [GH ES CLI usage documentation](https://github.com/github/gh-es/blob/main/USAGE.md#gh-es-replication-status)" and "[AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-command-line/administering-your-instance-using-the-github-cli)".
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion replication-management-api %}
|
||||
|
||||
## Monitoring replication using the REST API
|
||||
|
|
|
|||
|
|
@ -80,9 +80,9 @@ For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-ent
|
|||
|
||||
{% data variables.product.product_name %} runs a customized Linux operating system with only the necessary applications and services. {% data variables.product.company_short %} distributes patches for the instance's core operating system as part of its standard product release cycle. Patches address functionality, stability, and non-critical security issues for {% data variables.product.product_name %}. {% data variables.product.company_short %} also provides critical security patches as needed outside of the regular release cycle.
|
||||
|
||||
{% data variables.product.product_name %} is provided as an appliance, and many of the operating system packages are modified compared to the usual Debian distribution. We do not support modifying the underlying operating system for this reason (including operating system upgrades), which is aligned with the [{% data variables.product.prodname_ghe_server %} license and support agreement](https://enterprise.github.com/license), under section 11.3 Exclusions.
|
||||
{% data variables.product.product_name %} is provided as an appliance, and many of the operating system packages are modified compared to the usual {% ifversion ghes > 3.10 %}Ubuntu{% else %}Debian{% endif %} distribution. We do not support modifying the underlying operating system for this reason (including operating system upgrades), which is aligned with the [{% data variables.product.prodname_ghe_server %} license and support agreement](https://enterprise.github.com/license), under section 11.3 Exclusions.
|
||||
|
||||
Currently, the base operating system for {% data variables.product.product_name %} is Debian 10 (Buster), which receives support under the Debian Long Term Support program.
|
||||
Currently, the base operating system for {% data variables.product.product_name %} is {% ifversion ghes > 3.10 %}Ubuntu 20 (Focal Fossa){% else %}Debian 10 (Buster), which receives support under the Debian Long Term Support program{% endif %}.
|
||||
|
||||
Regular patch updates are released on the {% data variables.product.product_name %} [releases](https://enterprise.github.com/releases) page, and the [release notes](/admin/release-notes) page provides more information. These patches typically contain upstream vendor and project security patches after they've been tested and quality approved by our engineering team. There can be a slight time delay from when the upstream update is released to when it's tested and bundled in an upcoming {% data variables.product.product_name %} patch release.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,12 +2,13 @@
|
|||
title: Rules
|
||||
shortTitle: Rules
|
||||
intro: >-
|
||||
Use the REST API to manage rulesets for organizations. Organization
|
||||
rulesets control how people can interact with selected branches and tags in
|
||||
Use the REST API to manage rulesets for organizations. Organization rulesets
|
||||
control how people can interact with selected branches and tags in
|
||||
repositories in an organization.
|
||||
versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.11'
|
||||
topics:
|
||||
- API
|
||||
autogenerated: rest
|
||||
|
|
|
|||
|
|
@ -7,6 +7,7 @@ intro: >-
|
|||
versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.11'
|
||||
topics:
|
||||
- API
|
||||
autogenerated: rest
|
||||
|
|
|
|||
|
|
@ -1,9 +1,10 @@
|
|||
---
|
||||
title: Global security advisories
|
||||
intro: 'Use the REST API to view global security advisories.'
|
||||
intro: Use the REST API to view global security advisories.
|
||||
versions: # DO NOT MANUALLY EDIT. CHANGES WILL BE OVERWRITTEN BY A 🤖
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.11'
|
||||
topics:
|
||||
- API
|
||||
autogenerated: rest
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ intro: Use the REST API to view and manage security advisories.
|
|||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.11'
|
||||
topics:
|
||||
- API
|
||||
children:
|
||||
|
|
|
|||
|
|
@ -0,0 +1,4 @@
|
|||
# Reference: #11807
|
||||
# GH CLI extension for GHES Manage API
|
||||
versions:
|
||||
ghes: '>=3.11'
|
||||
|
|
@ -0,0 +1,138 @@
|
|||
- title: Access to package version deletion
|
||||
description: >-
|
||||
This preview adds support for the DeletePackageVersion mutation which
|
||||
enables deletion of private package versions.
|
||||
toggled_by: ':package-deletes-preview'
|
||||
announcement: null
|
||||
updates: null
|
||||
toggled_on:
|
||||
- Mutation.deletePackageVersion
|
||||
owning_teams:
|
||||
- '@github/pe-package-registry'
|
||||
- title: Deployments
|
||||
description: >-
|
||||
This preview adds support for deployments mutations and new deployments
|
||||
features.
|
||||
toggled_by: ':flash-preview'
|
||||
announcement: null
|
||||
updates: null
|
||||
toggled_on:
|
||||
- DeploymentStatus.environment
|
||||
- Mutation.createDeploymentStatus
|
||||
- CreateDeploymentStatusInput
|
||||
- CreateDeploymentStatusPayload
|
||||
- Mutation.createDeployment
|
||||
- CreateDeploymentInput
|
||||
- CreateDeploymentPayload
|
||||
owning_teams:
|
||||
- '@github/c2c-actions-service'
|
||||
- title: >-
|
||||
MergeInfoPreview - More detailed information about a pull request's merge
|
||||
state.
|
||||
description: >-
|
||||
This preview adds support for accessing fields that provide more detailed
|
||||
information about a pull request's merge state.
|
||||
toggled_by: ':merge-info-preview'
|
||||
announcement: null
|
||||
updates: null
|
||||
toggled_on:
|
||||
- PullRequest.canBeRebased
|
||||
- PullRequest.mergeStateStatus
|
||||
owning_teams:
|
||||
- '@github/pe-pull-requests'
|
||||
- title: UpdateRefsPreview - Update multiple refs in a single operation.
|
||||
description: This preview adds support for updating multiple refs in a single operation.
|
||||
toggled_by: ':update-refs-preview'
|
||||
announcement: null
|
||||
updates: null
|
||||
toggled_on:
|
||||
- Mutation.updateRefs
|
||||
- GitRefname
|
||||
- RefUpdate
|
||||
- UpdateRefsInput
|
||||
- UpdateRefsPayload
|
||||
owning_teams:
|
||||
- '@github/repos'
|
||||
- title: Access to a Repository's Dependency Graph
|
||||
description: This preview adds support for reading a dependency graph for a repository.
|
||||
toggled_by: ':hawkgirl-preview'
|
||||
announcement: null
|
||||
updates: null
|
||||
toggled_on:
|
||||
- DependencyGraphManifest
|
||||
- Repository.dependencyGraphManifests
|
||||
- DependencyGraphManifestEdge
|
||||
- DependencyGraphManifestConnection
|
||||
- DependencyGraphDependency
|
||||
- DependencyGraphDependencyEdge
|
||||
- DependencyGraphDependencyConnection
|
||||
- DependencyGraphPackageRelease.dependencies
|
||||
owning_teams:
|
||||
- '@github/dependency-graph'
|
||||
- title: Project Event Details
|
||||
description: >-
|
||||
This preview adds project, project card, and project column details to
|
||||
project-related issue events.
|
||||
toggled_by: ':starfox-preview'
|
||||
announcement: null
|
||||
updates: null
|
||||
toggled_on:
|
||||
- AddedToProjectEvent.project
|
||||
- AddedToProjectEvent.projectCard
|
||||
- AddedToProjectEvent.projectColumnName
|
||||
- ConvertedNoteToIssueEvent.project
|
||||
- ConvertedNoteToIssueEvent.projectCard
|
||||
- ConvertedNoteToIssueEvent.projectColumnName
|
||||
- MovedColumnsInProjectEvent.project
|
||||
- MovedColumnsInProjectEvent.projectCard
|
||||
- MovedColumnsInProjectEvent.projectColumnName
|
||||
- MovedColumnsInProjectEvent.previousProjectColumnName
|
||||
- RemovedFromProjectEvent.project
|
||||
- RemovedFromProjectEvent.projectColumnName
|
||||
owning_teams:
|
||||
- '@github/github-projects'
|
||||
- title: Labels Preview
|
||||
description: >-
|
||||
This preview adds support for adding, updating, creating and deleting
|
||||
labels.
|
||||
toggled_by: ':bane-preview'
|
||||
announcement: null
|
||||
updates: null
|
||||
toggled_on:
|
||||
- Mutation.createLabel
|
||||
- CreateLabelPayload
|
||||
- CreateLabelInput
|
||||
- Mutation.deleteLabel
|
||||
- DeleteLabelPayload
|
||||
- DeleteLabelInput
|
||||
- Mutation.updateLabel
|
||||
- UpdateLabelPayload
|
||||
- UpdateLabelInput
|
||||
owning_teams:
|
||||
- '@github/pe-pull-requests'
|
||||
- title: Import Project
|
||||
description: This preview adds support for importing projects.
|
||||
toggled_by: ':slothette-preview'
|
||||
announcement: null
|
||||
updates: null
|
||||
toggled_on:
|
||||
- Mutation.importProject
|
||||
owning_teams:
|
||||
- '@github/pe-issues-projects'
|
||||
- title: Team Review Assignments Preview
|
||||
description: >-
|
||||
This preview adds support for updating the settings for team review
|
||||
assignment.
|
||||
toggled_by: ':stone-crop-preview'
|
||||
announcement: null
|
||||
updates: null
|
||||
toggled_on:
|
||||
- Mutation.updateTeamReviewAssignment
|
||||
- UpdateTeamReviewAssignmentInput
|
||||
- TeamReviewAssignmentAlgorithm
|
||||
- Team.reviewRequestDelegationEnabled
|
||||
- Team.reviewRequestDelegationAlgorithm
|
||||
- Team.reviewRequestDelegationMemberCount
|
||||
- Team.reviewRequestDelegationNotifyTeam
|
||||
owning_teams:
|
||||
- '@github/pe-pull-requests'
|
||||
|
|
@ -0,0 +1,226 @@
|
|||
---
|
||||
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: 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: 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
|
||||
Разница между файлами не показана из-за своего большого размера
Загрузить разницу
|
|
@ -0,0 +1,338 @@
|
|||
date: '2023-11-07'
|
||||
release_candidate: true
|
||||
deprecated: false
|
||||
intro: |
|
||||
{% note %}
|
||||
|
||||
**Note:** Release candidate (RC) builds are intended solely for use in a test environment. 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.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
|
||||
|
||||
sections:
|
||||
features:
|
||||
- heading: Instance administration
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/3439
|
||||
- |
|
||||
Instance administrators can perform administrative tasks using the `gh es` extension for the GitHub CLI. The extension communicates with your instance's management API, so you don't need to SSH into the instance or write a custom application. For more information, see "[AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-command-line/administering-your-instance-using-the-github-cli)."
|
||||
|
||||
- heading: Authentication
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/3320
|
||||
- |
|
||||
To help users discover the required permissions for calls to a REST API endpoint, GitHub Enterprise Server returns the `X-Accepted-GitHub-Permissions` header for requests to endpoints that use fine-grained permissions, including requests from GitHub Apps. For more information, see the following articles.
|
||||
|
||||
- "[AUTOTITLE](/rest/overview/troubleshooting#insufficient-permissions-errors)"
|
||||
- "[AUTOTITLE](/rest/overview/permissions-required-for-fine-grained-personal-access-tokens)"
|
||||
- "[AUTOTITLE](/rest/overview/permissions-required-for-github-apps)
|
||||
|
||||
- heading: Audit logs
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/3263
|
||||
- |
|
||||
The web interface for enterprise, organization, and user audit logs include an expandable view that displays the full audit log payload for each event. Administrators and users can see the same event metadata when searching the audit log in the web interface or via streaming. For more information, see the following articles.
|
||||
|
||||
- "[AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)"
|
||||
- "[AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)"
|
||||
- "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)"
|
||||
|
||||
- heading: GitHub Advanced Security
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/3066
|
||||
- |
|
||||
On an instance with GitHub Actions enabled, in repositories that use default setup for code scanning, the default setup configuration updates automatically if GitHub detects new languages. Users can view a repository's language configuration for default setup from the repository's "Code security and analysis" settings page. Additionally, users can view information about setup and debug failed languages from the tools status page. For more information, see the following articles.
|
||||
|
||||
- "[AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning-at-scale#about-adding-languages-to-an-existing-default-setup-configuration)"
|
||||
- "[AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning)"
|
||||
- "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-the-tool-status-page)"
|
||||
|
||||
# https://github.com/github/releases/issues/3258
|
||||
- |
|
||||
On an instance with GitHub Actions enabled, default setup for code scanning at the organization level is now generally available. For more information, see "[AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning-at-scale)" and "[AUTOTITLE](/rest/orgs/orgs?apiVersion=2022-11-28#enable-or-disable-a-security-feature-for-an-organization)" in the REST API documentation.
|
||||
|
||||
# https://github.com/github/releases/issues/3214
|
||||
- |
|
||||
On an instance with GitHub Actions enabled, during configuration of default setup for code scanning, users can select either the "Extended" or "Default" query suite for eligible repositories in an organization. For more information, see "[AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/built-in-codeql-query-suites)" and "[AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning)."
|
||||
|
||||
# https://github.com/github/releases/issues/2841
|
||||
- |
|
||||
On an instance with GitHub Actions enabled, to better protect active and inactive repositories, GitHub Enterprise Server automatically analyzes repositories that use a default setup for code scanning. The analysis runs on a weekly schedule and uses the most recent version of CodeQL. When configuring code scanning, the fixed time for the weekly scan is randomly chosen. The scan will take place at the same time every week, and the schedule is displayed after the setup is completed, so users can easily see when the next scheduled analysis will occur. The scheduled analysis will be automatically disabled if a repository has no activity for six months. Creation of a pull request or pushes to the repository will re-enable scheduled analysis.
|
||||
|
||||
# https://github.com/github/releases/issues/3283
|
||||
- |
|
||||
Code scanning default setup is available for Swift analysis with CodeQL. For more information, see "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning-for-a-repository#configuring-code-scanning-automatically)."
|
||||
|
||||
# https://github.com/github/releases/issues/3355
|
||||
- |
|
||||
CodeQL 2.14.6 and later supports analysis of code written in Go 1.21. For more information, see "[Supported languages and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/)" in the CodeQL documentation.
|
||||
|
||||
# https://github.com/github/releases/issues/3289
|
||||
- |
|
||||
With CodeQL model packs for Java, users can improve code scanning results by ensuring that any custom Java libraries and frameworks used by their codebase are recognized by CodeQL. For more information, see the following documentation.
|
||||
|
||||
- "[AUTOTITLE](/code-security/code-scanning/managing-your-code-scanning-configuration/editing-your-configuration-of-default-setup#extending-codeql-coverage-with-codeql-model-packs-in-default-setup)"
|
||||
- "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning#extending-codeql-coverage-with-codeql-model-packs)"
|
||||
- "[Using the CodeQL model editor](https://codeql.github.com/docs/codeql-for-visual-studio-code/using-the-codeql-model-editor)" in the CodeQL documentation
|
||||
|
||||
# https://github.com/github/releases/issues/3110
|
||||
- |
|
||||
For instances with GitHub Connect configured, code scanning with CodeQL supports Java codebases that use [Project Lombok](https://projectlombok.org/). Previously, code scanning users were able to scan Java applications that contained Lombok code, but all the contents of files containing Lombok code were either skipped or users had to apply a workaround to prepare the applications for scanning. Lombok features will now be automatically scanned without requiring any workaround.
|
||||
|
||||
For more information about syncing the required GitHub Actions workflow to scan Lombok code, see "[AUTOTITLE](/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)."
|
||||
|
||||
# https://github.com/github/releases/issues/2920
|
||||
- |
|
||||
Push protection for secret scanning is now generally available. For more information, see "[AUTOTITLE](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
|
||||
|
||||
# https://github.com/github/releases/issues/2649
|
||||
# https://github.com/github/releases/issues/2866
|
||||
# https://github.com/github/releases/issues/3196
|
||||
- |
|
||||
To prevent the leak of tokens where users work outside of code, secret scanning detects tokens in both new and historical issue titles, descriptions, and comments. When a new token type is added to secret scanning, GitHub Enterprise Server scans for matches automatically. This expanded coverage also detects and surfaces secrets that match any custom pattern defined at the repository, organization, or enterprise level. These secrets appear both in the web interface and in queries to the REST API. For more information, see "[AUTOTITLE](/code-security/secret-scanning/about-secret-scanning)" and "[AUTOTITLE](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
|
||||
|
||||
# https://github.com/github/releases/issues/2868
|
||||
- |
|
||||
Users can view metrics associated with push protection usage across an organization. The overview shows a summary of blocks and bypasses, as well as more granular metrics. For more information, see "[AUTOTITLE](/code-security/security-overview/assessing-code-security-risk)."
|
||||
|
||||
# https://github.com/github/releases/issues/3291
|
||||
- |
|
||||
A new REST API endpoint is available for dataflow analysis using custom CodeQL queries. The new endpoint offers additional flexibility, includes improvements that prevent common pitfalls with the old API, and improves the performance of query evaluation by five percent. For more information, see [New dataflow API for writing custom CodeQL queries](https://github.blog/changelog/2023-08-14-new-dataflow-api-for-writing-custom-codeql-queries/) in the GitHub Changelog.
|
||||
|
||||
- heading: Dependabot
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/2919
|
||||
- |
|
||||
For developers who manage Node.js dependencies using the pnpm package manager, pnpm is fully supported by dependency graph, Dependabot alerts, and Dependabot security updates. For more information about securing your supply chain with Dependabot, see "[AUTOTITLE](/code-security/dependabot)."
|
||||
|
||||
# https://github.com/github/releases/issues/3171
|
||||
- |
|
||||
Developers can enforce policies related to vulnerabilities and licenses in pull requests for complex ecosystems with transitive dependencies like Gradle and Scala. Dependency review supports dependencies from the dependency submission API. For more information, see the following articles.
|
||||
|
||||
- "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#best-practices-for-using-the-dependency-review-api-and-the-dependency-submission-api-together)"
|
||||
- "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)"
|
||||
- "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)"
|
||||
|
||||
# https://github.com/github/releases/issues/3268
|
||||
# https://github.com/github/releases/issues/3362
|
||||
# https://github.com/github/releases/issues/3363
|
||||
# https://github.com/github/releases/issues/3364
|
||||
- |
|
||||
To control how Dependabot structures pull requests and improve mergeability, users can implement flexible grouping options in `dependabot.yml`. You can also control Dependabot's behavior for groups using comment commands. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#groups)" and "[AUTOTITLE](/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)."
|
||||
|
||||
# https://github.com/github/releases/issues/3270
|
||||
# https://github.com/github/releases/issues/3271
|
||||
- |
|
||||
Dependabot can open pull requests for Swift and Gradle dependencies.
|
||||
|
||||
- Users can also configure scheduled updates for Swift dependencies using `dependabot.yml`.
|
||||
- If users have used the REST API for dependency submission to upload Gradle dependencies to the dependency graph and receive Dependabot alerts for those dependencies, Dependabot will try to open a pull request to resolve security updates enabled for the repository.
|
||||
|
||||
For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)."
|
||||
|
||||
# https://github.com/github/releases/issues/3287
|
||||
- |
|
||||
Responses from REST API endpoints for repositories display whether Dependabot security updates are enabled or disabled. Users can also enable or disable security updates for a repository using the REST API. For more information, see "[AUTOTITLE](/rest/repos/repos)" in the REST API documentation.
|
||||
|
||||
- heading: Code security
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/3259
|
||||
- |
|
||||
To assess risks to code security and ensure adoption of features to improve code security, the "Security risk" and "Security coverage" pages for organizations and the entire instance are generally available. Additionally, the alert-centric pages for Dependabot, code scanning, and secret scanning are also now generally available. For more information, see "[Assessing your code security risk](/code-security/security-overview/assessing-code-security-risk)" and "[Assessing adoption of code security features](/code-security/security-overview/assessing-adoption-code-security)."
|
||||
|
||||
# https://github.com/github/releases/issues/3126
|
||||
- |
|
||||
Users can take advantage of the [GitHub Advisory Database](https://github.com/advisories) using the REST API. The Advisory Database is a free, open-source list of actionable security advisories and CVEs. API responses include machine-readable mappings to the ecosystem, package name, and affected versions of impacted software. For more information, see "[AUTOTITLE](/rest/security-advisories/global-advisories)" in the REST API documentation.
|
||||
|
||||
- heading: GitHub Actions
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/3247
|
||||
- |
|
||||
To better navigate, trace, understand, and monitor deployments, users can view and track the full history of deployments in a repository or filter across environments. For more information, see "[AUTOTITLE](/actions/deployment/managing-your-deployments/viewing-deployment-history)."
|
||||
|
||||
# https://github.com/github/releases/issues/3402
|
||||
- |
|
||||
Users can improve the security of deployment environments by configuring a branch protection policy to only allow specific branches to deploy to an environment. Additionally, the following security improvements apply to environments.
|
||||
|
||||
- GitHub Enterprise Server blocks runs triggered from forks with branch names that match the protected branch's name.
|
||||
- Tags with the same name as a protected branch cannot deploy to the environments with a branch protection configuration.
|
||||
|
||||
For more information, see "[AUTOTITLE](/actions/deployment/targeting-different-environments/using-environments-for-deployment#deployment-branches)."
|
||||
|
||||
# https://github.com/github/releases/issues/3489
|
||||
- |
|
||||
On an instance with GitHub Actions enabled and a configuration for deployment environments, administrators for environments can improve the security of deployments by enforcing a review by someone other than the person who triggered the run. This option prevents required reviewers from self-reviewing to trigger workflows. For more information, see "[AUTOTITLE](/actions/deployment/targeting-different-environments/using-environments-for-deployment#required-reviewers)."
|
||||
|
||||
- heading: Organizations
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/3465
|
||||
- |
|
||||
Organization owners can signal that an organization is no longer actively maintained by archiving the organization. For more information, see "[AUTOTITLE](/organizations/managing-organization-settings/archiving-an-organization)."
|
||||
|
||||
- heading: Repositories
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/2926
|
||||
- |
|
||||
Users can govern protections for branches and tags in a repository using repository rules. To govern the protections for all of an organization's repositories, users can also enable rulesets for an organization. Contributors to a repository can see which rules apply via the web interface, Git, or the GitHub CLI. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets)."
|
||||
|
||||
# https://github.com/github/releases/issues/3081
|
||||
- |
|
||||
Users can create new repositories with predefined attributes using query parameters. For example, a user can create a URL that prepopulates information about the repository like the name, description, visibility, and more. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/creating-a-new-repository#creating-a-new-repository-from-a-url-query)."
|
||||
|
||||
# https://github.com/github/releases/issues/2741
|
||||
- |
|
||||
Users can more easily understand changes to a repository using the actiity view. For more information, see "[AUTOTITLE](/repositories/viewing-activity-and-data-for-your-repository/using-the-activity-view-to-see-changes-to-a-repository)."
|
||||
|
||||
- heading: Issues
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/3324
|
||||
- |
|
||||
Users can automatically add a new issue to projects using a custom issue form by defining `projects` in the issue template. For more information, see "[AUTOTITLE](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms)."
|
||||
|
||||
- heading: Projects
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/3205
|
||||
- |
|
||||
Users can review items in a project view broken down by a certain field value. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-table-layout#slicing-by-field-values)."
|
||||
|
||||
# https://github.com/github/releases/issues/3205
|
||||
- |
|
||||
Users can create charts to visualize current project items, or visualize project items over time. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects)."
|
||||
|
||||
- heading: Accessibility
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/3340
|
||||
- |
|
||||
To improve the visibility of links with blocks of text in the web interface for GitHub Enterprise Server, users can apply underline styling. For more information, see "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-accessibility-settings#managing-the-appearance-of-links)."
|
||||
|
||||
changes:
|
||||
# https://github.com/github/releases/issues/3319
|
||||
- |
|
||||
The speed of restoration operations with GitHub Enterprise Server Backup Utilities has increased.
|
||||
|
||||
# https://github.com/github/releases/issues/3403
|
||||
- |
|
||||
Field names for some service logs on GitHub Enterprise Server have changed as part of GitHub's gradual migration to internal semantic conventions for [OpenTelemetry](https://opentelemetry.io/). Additional field names were changed in GitHub Enterprise Server 3.9 and 3.10. If any tooling or processes in your environment rely on specific field names within logs, or log entries in specific files, the following changes may affect you.
|
||||
|
||||
- `level` is now `SeverityText`.
|
||||
- `log_message`, `msg`, or `message` is now `Body`.
|
||||
- `now` is now `Timestamp`.
|
||||
- Custom field names such as `gh.repo.id` or `graphql.operation.name` use semantic names.
|
||||
- Log statements that the instance would previously write to `auth.log`, `ldap.log`, or `ldap-sync.log` now appear in containerized logs for `github-unicorn` if the statement originated from a web request, or in logs for `github-resqued` if the statement originated from a background job. For more information about containerized logs, see "[AUTOTITLE](/admin/monitoring-managing-and-updating-your-instance/monitoring-your-appliance/about-system-logs#system-logs-in-the-systemd-journal)."
|
||||
|
||||
For a full list of mappings, download the OpenTelemetry attribute mapping CSV for GitHub Enterprise Server [3.9](/assets/ghes-3.9-opentelemetry-attribute-mappings.csv), [3.10](/assets/ghes-3.10-opentelemetry-attribute-mappings.csv), and [3.11](/assets/ghes-3.11-opentelemetry-attribute-mappings.csv).
|
||||
|
||||
# https://github.com/github/releases/issues/3281
|
||||
- |
|
||||
On an instance that uses built-in authentication or LDAP, if two-factor authentication (2FA) is configured for an organization, a user could use a TOTP code multiple times within the code's window of validity during authentication or when entering sudo mode for sensitive actions. To improve security, this reuse is no longer allowed. External systems with a scripted login flow across multiple parallel jobs may stop working as a result of this change.
|
||||
|
||||
For more information about 2FA, see the following articles.
|
||||
|
||||
- "[AUTOTITLE](/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)"
|
||||
- "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/sudo-mode)"
|
||||
- "[AUTOTITLE](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-totp-mobile-app)"
|
||||
|
||||
# https://github.com/github/releases/issues/3327
|
||||
- |
|
||||
On an instance with a GitHub Advanced Security license, during analysis of Python projects with code scanning using CodeQL and an advanced setup, GitHub Enterprise Server would automatically install dependencies for the project. Due to improvements to CodeQL, GitHub Enterprise Server no longer needs to fetch these dependencies to analyze a codebase. To improve scan times for Python projects, automatic dependency installation is disabled.
|
||||
|
||||
If you configured code scanning with CodeQL via advanced setup to disable dependency installation, GitHub recommends setting `setup-python-dependencies` to `false` for the configuration. For more information, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning#analyzing-python-dependencies)."
|
||||
|
||||
# https://github.com/github/releases/issues/3172
|
||||
- |
|
||||
On an instance with Dependabot enabled, due to misconfiguration or incompatible versions, Dependabot jobs for a repository can fail. After 30 failed runs, subsequent scheduled jobs will fail immediately until you trigger a check for updates from the dependency graph, or until you update a manifest file. Jobs for Dependabot security updates will still trigger normally.
|
||||
|
||||
# https://github.com/github/releases/issues/3284
|
||||
- |
|
||||
On an instance with GitHub Advanced Security, to help users more efficiently review and filter code scanning alerts at scale using the REST API, the `updated_at` field in API responses is improved. The `updated_at` timestamp now represents an alert's most recent state change on the branch that you requested. State changes include an alert being introduced, fixed, dismissed, reopened, or reintroduced. Previously, the `updated_at` timestamp changed frequently, whenever an alert was found in an analysis or the alert state changed. For more information about using the REST API to retrieve code scanning alerts, see "[AUTOTITLE](/rest/code-scanning/code-scanning?apiVersion=2022-11-28)" in the REST API documentation.
|
||||
|
||||
# https://github.com/github/releases/issues/2874
|
||||
- |
|
||||
On an instance with Dependabot enabled, the following improvements apply to the repository view for dependency graph, available from the repository's "Insights" tab.
|
||||
|
||||
- Users can search by package name from a paginated list of all dependencies.
|
||||
- Dependency licenses are displayed.
|
||||
- Dependabot alerts appear for dependencies, sorted by severity, and link to the Dependabot alerts and the Dependabot update pull request where applicable.
|
||||
|
||||
For more information about the dependency graph, see "[AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
|
||||
|
||||
# https://github.com/github/releases/issues/3253
|
||||
- |
|
||||
After first enabling Dependabot on an instance, GitHub Enterprise Server will no longer send web or email notifications for repositories that are initially populated with Dependabot alerts. This allows you to review the new Dependabot alerts for a repository, organization, or the entire instance without immediately notifying other users of existing alerts.
|
||||
|
||||
# https://github.com/github/releases/issues/2603
|
||||
- |
|
||||
On an instance with GitHub Actions enabled, workflows that use Node.js 12 will log a warning. Node.js 12 has been end-of-life since [April 2022](https://github.com/nodejs/Release/#end-of-life-releases).
|
||||
|
||||
- Workflow authors should update actions to run on Node.js 16 instead of 12. For more information, see "[AUTOTITLE](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-javascript-actions)."
|
||||
- Users with workflows that use Node.js should specify Node.js 16 or later in the workflows using versioned actions. For more information, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#example-using-versioned-actions)."
|
||||
|
||||
# https://github.com/github/releases/issues/3500
|
||||
- |
|
||||
On an instance with GitHub Actions enabled and runners using GitHub Actions Runner 2.309.0 or later, users can no longer use `GITHUB_ENV` to set the `NODE_OPTIONS` environment variable in workflows. Workflows that set `NODE_OPTIONS` as an environment variable will now log the following error. For more information, see "[AUTOTITLE](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-environment-variable)" and the [v2.309.0 release](https://github.com/actions/runner/releases/tag/v2.309.0) in the actions/runner repository on GitHub.com.
|
||||
|
||||
```
|
||||
Can't store NODE_OPTIONS output parameter using '$GITHUB_ENV' command.
|
||||
```
|
||||
|
||||
# https://github.com/github/releases/issues/3205
|
||||
- |
|
||||
Users can quickly take action on multiple items in a group, or the group itself, using the `•••` button in a table, board, or roadmap.
|
||||
|
||||
# https://github.com/github/releases/issues/3219
|
||||
- |
|
||||
Users can break out items in a project by workstreams, team members, priorities, or other groupings using a swimlane view. For more information, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-board-layout#grouping-by-field-values)."
|
||||
|
||||
# https://github.com/github/releases/issues/3262
|
||||
- |
|
||||
Users can view view the template used to create a project from a project's settings.
|
||||
|
||||
# https://github.com/github/releases/issues/3262
|
||||
- |
|
||||
When scrolling through a project, group headers are now sticky.
|
||||
|
||||
# https://github.com/github/releases/issues/3262
|
||||
- |
|
||||
The colors for single-select fields in a project have been updated, so users see the same colors within the field picker and within project views.
|
||||
|
||||
# https://github.com/github/releases/issues/3262
|
||||
- |
|
||||
Users create can create issues in a project view that's grouped by repository in the board layout by clicking "Create new issue", or by starting to type the issue's title.
|
||||
|
||||
known_issues:
|
||||
- |
|
||||
Custom firewall rules are removed during the upgrade process.
|
||||
- |
|
||||
During the validation phase of a configuration run, a `No such object` error may occur for the Notebook and Viewscreen services. This error can be ignored as the services should still correctly start.
|
||||
- |
|
||||
If the root site administrator is locked out of the Management Console after failed login attempts, the account does not unlock automatically after the defined lockout time. Someone with administrative SSH access to the instance must unlock the account using the administrative shell. For more information, see "[AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/troubleshooting-access-to-the-management-console#unlocking-the-root-site-administrator-account)."
|
||||
- |
|
||||
If an instance is configured to forward logs to a target server with TLS enabled, certificate authority (CA) bundles that a site administrator uploads using `ghe-ssl-ca-certificate-install` are not respected, and connections to the server fail.
|
||||
- |
|
||||
The `mbind: Operation not permitted` error in the `/var/log/mysql/mysql.err` file can be ignored. MySQL 8 does not gracefully handle when the `CAP_SYS_NICE` capability isn't required, and outputs an error instead of a warning.
|
||||
- |
|
||||
On an instance hosted in AWS, system time may lose synchronization with Amazon's servers after an administrator reboots the instance.
|
||||
- |
|
||||
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 %}
|
||||
- |
|
||||
{% data reusables.release-notes.2023-11-cluster-ha-failover-git-push-failure %}
|
||||
- |
|
||||
On an instance in a high-availability configuration, passive replica nodes accept Git client requests and forward the requests to the primary node.
|
||||
- |
|
||||
On an instance with the HTTP `X-Forwarded-For` header configured for use behind a load balancer, all client IP addresses in the instance's audit log erroneously appear as 127.0.0.1.
|
||||
- |
|
||||
{% data reusables.release-notes.2023-10-git-push-made-but-not-registered %}
|
||||
|
||||
deprecations:
|
||||
# https://github.com/github/releases/issues/2605
|
||||
- heading: Dependabot updates no longer support Python 3.6 or 3.7
|
||||
notes:
|
||||
- |
|
||||
Dependabot updates no longer support Python 3.6 or 3.7, which have reached end-of-life. If a user's code uses these versions, Dependabot will no longer be able to open pull requests in your repository and will log errors. Update to Python 3.8 or later to ensure your code is secure and Dependabot can still run.
|
||||
|
||||
Users will continue to receive Dependabot alerts for dependencies with known vulnerabilities. To resolve these alerts, users can manually upgrade the affected package.
|
||||
|
||||
For more information about Python releases, see [Status of Python versions](https://devguide.python.org/versions) on the Python website. For more information about supported package managers for Dependabot, see "[AUTOTITLE](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates#supported-repositories-and-ecosystems)."
|
||||
|
|
@ -0,0 +1 @@
|
|||
After failing over an instance in a cluster configuration, Git pushes to the instance will fail. This issue impacts pushes from the command line as well as the web interface. To resolve this issue, [contact GitHub Support](https://support.github.com/contact).
|
||||
|
|
@ -1 +1 @@
|
|||
version: ''
|
||||
version: enterprise-server@3.11
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
version: ''
|
||||
version: enterprise-server@3.11
|
||||
|
|
|
|||
Разница между файлами не показана из-за своего большого размера
Загрузить разницу
Разница между файлами не показана из-за своего большого размера
Загрузить разницу
Разница между файлами не показана из-за своего большого размера
Загрузить разницу
Разница между файлами не показана из-за своего большого размера
Загрузить разницу
Разница между файлами не показана из-за своего большого размера
Загрузить разницу
|
|
@ -60,5 +60,5 @@
|
|||
"2022-11-28"
|
||||
]
|
||||
},
|
||||
"sha": "0dc810ce5cafe80f762c6a76f52961717c61ce00"
|
||||
"sha": "b82b3990d4d99dfecec33caa6e8715985dbadedf"
|
||||
}
|
||||
|
|
@ -0,0 +1,149 @@
|
|||
[
|
||||
{
|
||||
"title": "Access to package version deletion preview",
|
||||
"description": "This preview adds support for the DeletePackageVersion mutation which enables deletion of private package versions.",
|
||||
"toggled_by": "package-deletes-preview",
|
||||
"toggled_on": [
|
||||
"Mutation.deletePackageVersion"
|
||||
],
|
||||
"owning_teams": [
|
||||
"@github/pe-package-registry"
|
||||
],
|
||||
"accept_header": "application/vnd.github.package-deletes-preview+json",
|
||||
"href": "/graphql/overview/schema-previews#access-to-package-version-deletion-preview"
|
||||
},
|
||||
{
|
||||
"title": "Deployments preview",
|
||||
"description": "This preview adds support for deployments mutations and new deployments features.",
|
||||
"toggled_by": "flash-preview",
|
||||
"toggled_on": [
|
||||
"DeploymentStatus.environment",
|
||||
"Mutation.createDeploymentStatus",
|
||||
"Mutation.createDeployment"
|
||||
],
|
||||
"owning_teams": [
|
||||
"@github/c2c-actions-service"
|
||||
],
|
||||
"accept_header": "application/vnd.github.flash-preview+json",
|
||||
"href": "/graphql/overview/schema-previews#deployments-preview"
|
||||
},
|
||||
{
|
||||
"title": "Merge info preview more detailed information about a pull request's merge state preview",
|
||||
"description": "This preview adds support for accessing fields that provide more detailed information about a pull request's merge state.",
|
||||
"toggled_by": "merge-info-preview",
|
||||
"toggled_on": [
|
||||
"PullRequest.canBeRebased",
|
||||
"PullRequest.mergeStateStatus"
|
||||
],
|
||||
"owning_teams": [
|
||||
"@github/pe-pull-requests"
|
||||
],
|
||||
"accept_header": "application/vnd.github.merge-info-preview+json",
|
||||
"href": "/graphql/overview/schema-previews#merge-info-preview-more-detailed-information-about-a-pull-requests-merge-state-preview"
|
||||
},
|
||||
{
|
||||
"title": "Update refs preview update multiple refs in a single operation preview",
|
||||
"description": "This preview adds support for updating multiple refs in a single operation.",
|
||||
"toggled_by": "update-refs-preview",
|
||||
"toggled_on": [
|
||||
"Mutation.updateRefs",
|
||||
"GitRefname",
|
||||
"RefUpdate"
|
||||
],
|
||||
"owning_teams": [
|
||||
"@github/repos"
|
||||
],
|
||||
"accept_header": "application/vnd.github.update-refs-preview+json",
|
||||
"href": "/graphql/overview/schema-previews#update-refs-preview-update-multiple-refs-in-a-single-operation-preview"
|
||||
},
|
||||
{
|
||||
"title": "Access to a repository's dependency graph preview",
|
||||
"description": "This preview adds support for reading a dependency graph for a repository.",
|
||||
"toggled_by": "hawkgirl-preview",
|
||||
"toggled_on": [
|
||||
"DependencyGraphManifest",
|
||||
"Repository.dependencyGraphManifests",
|
||||
"DependencyGraphManifestEdge",
|
||||
"DependencyGraphManifestConnection",
|
||||
"DependencyGraphDependency",
|
||||
"DependencyGraphDependencyEdge",
|
||||
"DependencyGraphDependencyConnection",
|
||||
"DependencyGraphPackageRelease.dependencies"
|
||||
],
|
||||
"owning_teams": [
|
||||
"@github/dependency-graph"
|
||||
],
|
||||
"accept_header": "application/vnd.github.hawkgirl-preview+json",
|
||||
"href": "/graphql/overview/schema-previews#access-to-a-repositorys-dependency-graph-preview"
|
||||
},
|
||||
{
|
||||
"title": "Project event details preview",
|
||||
"description": "This preview adds project, project card, and project column details to project-related issue events.",
|
||||
"toggled_by": "starfox-preview",
|
||||
"toggled_on": [
|
||||
"AddedToProjectEvent.project",
|
||||
"AddedToProjectEvent.projectCard",
|
||||
"AddedToProjectEvent.projectColumnName",
|
||||
"ConvertedNoteToIssueEvent.project",
|
||||
"ConvertedNoteToIssueEvent.projectCard",
|
||||
"ConvertedNoteToIssueEvent.projectColumnName",
|
||||
"MovedColumnsInProjectEvent.project",
|
||||
"MovedColumnsInProjectEvent.projectCard",
|
||||
"MovedColumnsInProjectEvent.projectColumnName",
|
||||
"MovedColumnsInProjectEvent.previousProjectColumnName",
|
||||
"RemovedFromProjectEvent.project",
|
||||
"RemovedFromProjectEvent.projectColumnName"
|
||||
],
|
||||
"owning_teams": [
|
||||
"@github/github-projects"
|
||||
],
|
||||
"accept_header": "application/vnd.github.starfox-preview+json",
|
||||
"href": "/graphql/overview/schema-previews#project-event-details-preview"
|
||||
},
|
||||
{
|
||||
"title": "Labels preview",
|
||||
"description": "This preview adds support for adding, updating, creating and deleting labels.",
|
||||
"toggled_by": "bane-preview",
|
||||
"toggled_on": [
|
||||
"Mutation.createLabel",
|
||||
"Mutation.deleteLabel",
|
||||
"Mutation.updateLabel"
|
||||
],
|
||||
"owning_teams": [
|
||||
"@github/pe-pull-requests"
|
||||
],
|
||||
"accept_header": "application/vnd.github.bane-preview+json",
|
||||
"href": "/graphql/overview/schema-previews#labels-preview"
|
||||
},
|
||||
{
|
||||
"title": "Import project preview",
|
||||
"description": "This preview adds support for importing projects.",
|
||||
"toggled_by": "slothette-preview",
|
||||
"toggled_on": [
|
||||
"Mutation.importProject"
|
||||
],
|
||||
"owning_teams": [
|
||||
"@github/pe-issues-projects"
|
||||
],
|
||||
"accept_header": "application/vnd.github.slothette-preview+json",
|
||||
"href": "/graphql/overview/schema-previews#import-project-preview"
|
||||
},
|
||||
{
|
||||
"title": "Team review assignments preview",
|
||||
"description": "This preview adds support for updating the settings for team review assignment.",
|
||||
"toggled_by": "stone-crop-preview",
|
||||
"toggled_on": [
|
||||
"Mutation.updateTeamReviewAssignment",
|
||||
"TeamReviewAssignmentAlgorithm",
|
||||
"Team.reviewRequestDelegationEnabled",
|
||||
"Team.reviewRequestDelegationAlgorithm",
|
||||
"Team.reviewRequestDelegationMemberCount",
|
||||
"Team.reviewRequestDelegationNotifyTeam"
|
||||
],
|
||||
"owning_teams": [
|
||||
"@github/pe-pull-requests"
|
||||
],
|
||||
"accept_header": "application/vnd.github.stone-crop-preview+json",
|
||||
"href": "/graphql/overview/schema-previews#team-review-assignments-preview"
|
||||
}
|
||||
]
|
||||
Разница между файлами не показана из-за своего большого размера
Загрузить разницу
|
|
@ -0,0 +1,258 @@
|
|||
{
|
||||
"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-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-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"
|
||||
}
|
||||
]
|
||||
}
|
||||
Различия файлов скрыты, потому что одна или несколько строк слишком длинны
|
|
@ -11,6 +11,9 @@
|
|||
],
|
||||
"ghes-3.10": [
|
||||
"2022-11-28"
|
||||
],
|
||||
"ghes-3.11": [
|
||||
"2022-11-28"
|
||||
]
|
||||
},
|
||||
"versionMapping": {
|
||||
|
|
@ -36,5 +39,5 @@
|
|||
]
|
||||
}
|
||||
},
|
||||
"sha": "0dc810ce5cafe80f762c6a76f52961717c61ce00"
|
||||
"sha": "b82b3990d4d99dfecec33caa6e8715985dbadedf"
|
||||
}
|
||||
|
|
@ -9,10 +9,10 @@ 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.11'
|
||||
export const nextNext = '3.12'
|
||||
export const next = '3.12'
|
||||
export const nextNext = '3.13'
|
||||
|
||||
export const supported = ['3.10', '3.9', '3.8', '3.7', '3.6']
|
||||
export const supported = ['3.11', '3.10', '3.9', '3.8', '3.7', '3.6']
|
||||
|
||||
// Ensure that:
|
||||
// "next" is ahead of "latest" by one minor or major release.
|
||||
|
|
|
|||
Разница между файлами не показана из-за своего большого размера
Загрузить разницу
|
|
@ -1,3 +1,3 @@
|
|||
{
|
||||
"sha": "0dc810ce5cafe80f762c6a76f52961717c61ce00"
|
||||
"sha": "b82b3990d4d99dfecec33caa6e8715985dbadedf"
|
||||
}
|
||||
Загрузка…
Ссылка в новой задаче