Frecuentemente publicamos actualizaciones de nuestra documentación. Es posible que la traducción de esta página esté en curso. Para conocer la información más actual, visita la documentación en inglés. Si existe un problema con las traducciones en esta página, por favor infórmanos.
2.22

3.0 Release notes

Enterprise Server 3.0.0

Download

February 16, 2021

The minimum infrastructure requirements have increased for Servidor de GitHub Enterprise 3.0+. For more information, see "About minimum requirements for GitHub Enterprise Server 3.0 and later."

  • GitHub Actions

    • GitHub Actions is now generally available on Servidor de GitHub Enterprise 3.0+. Build, test, and deploy your code from GitHub. Submit code reviews, branch management, and issue triaging work the way you want.

      This release includes several improvements from the beta of GitHub Actions on Servidor de GitHub Enterprise:

      GitHub Actions is not currently supported for enterprises using cluster configurations.

  • GitHub Packages

    • Paquetes de GitHub is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an end-to-end DevOps workflow that includes your code, continuous integration, and deployment solutions.

      Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the updated minimum requirements for your platform before you turn on Paquetes de GitHub.

      When publishing packages to NuGet, users can now use the --api-key option to pass their authentication token instead of writing it into a file. For more information, see Configuring dotnet CLI for use with GitHub Packages

      Paquetes de GitHub is not currently supported for enterprises using cluster configurations.

  • GitHub Mobile beta

    • GitHub para móvil beta allows you to triage notifications and manage issues and pull requests from your device. You can be simultaneously signed into mobile with one user account on GitHub.com and one user account on Servidor de GitHub Enterprise.

      GitHub para móvil beta is now available for Servidor de GitHub Enterprise. Sign in with our Android and iOS apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running ghe-config app.mobile.enabled false.

  • Advanced Security Secret Scanning beta

    • Secret Scanning beta scans public and private repositories for committed credentials, finds secrets, and notifies the secret provider or admin the moment they are committed into a repository.

      Administrators using GitHub Advanced Security can enable and configure GitHub Advanced Security secret scanning. You can review the updated minimum requirements for your platform before you turn on GitHub Advanced Security secret scanning.

  • Advanced Security Code Scanning

    • GitHub Advanced Security code scanning is now generally available on GitHub Enterprise Server. Organizations who have purchased Advanced Security can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "Configuring code scanning on your appliance"

  • Administration Changes

    • The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. It also uses less CPU and memory in Servidor de GitHub Enterprise 3.0+.

    • Organization and Enterprise owners can now see when a team member has been promoted to or demoted from being a team maintainer in the audit log through the new team.promote_maintainer and team.demote_maintainer audit log events. For more information, see "Audited actions."

    • Repository maintainers with existing Páginas de GitHub sites can easily update their prior default branch name.

    • Additional hardware resources are required to run Servidor de GitHub Enterprise with any of Actions, Packages or Advanced Security enabled. For more infomation on the minimum required resources for each supported platform, see "Setting up a Servidor de GitHub Enterprise instance."

    • Administrators can now publish a message, which all users must accept. This can help to onboard new users and surface other organization-specific information and policies.

  • Security Changes

    • Organization owners can now disable publication of Páginas de GitHub sites from repositories in the organization. Disabling Páginas de GitHub for the organization will prevent members from creating new Pages sites but will not unpublish existing sites. For more information, see "Disabling publication of Páginas de GitHub sites for your organization."

    • A datacenter must be explicitly defined on all nodes before enabling an active replica.

    • All usage of SSH fingerprints has been switched to use SHA256 fingerprints as they are used with OpenSSH since version 6.8 as well. This applies to the web interface and also the API where fingerprints are returned such as in GraphQL. The fingerprints follow the OpenSSH format.

    • SHA-1 and SHA-256 signature headers (two headers) are sent on webhooks.

  • Developer Changes

    • Majority of the services running in Servidor de GitHub Enterprise 3.0+ are now on containers which internally enables GitHub to iterate fast and ship high quality releases

    • The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages.

  • API Changes

    • Administrators can now configure and manage the site-wide announcement banner via the REST API. For more information, see the endpoints for "GitHub Enterprise administration."

    • A new API endpoint enables the exchange of a user to server token for a user to server token scoped to specific repositories. For more information, see "Apps" in the GitHub REST API documentation.

  • Default branch renaming

    • Enterprise and organization administrators can now set the default branch name for new repositories. Enterprise administrators can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own.

      Existing repositories are unaffected by these settings, and their default branch name will not be changed.

      The default branch for newly-created repositories will be set to main in GHES 3.1, unless you opt out by setting the default branch setting at the enterprise level.

      This change is one of many changes GitHub is making to support projects and maintainers that want to rename their default branch. To learn more about the changes we're making, see github/renaming.

  • Fixes for known issues from Release Candidates

    • All known issues from Release Candidate 1 and Release Candidate 2 have been fixed, except those listed in the Known Issues section below.

  • Fixes for other issues

    • Issues with migrations and upgrades to 3.0.0 have been fixed.

    • Backup Utilities versioning now works for release candidate versions.

    • Generating a support bundle resulted in an error in the orchestrator logs.

    • A large restore could result in Redis running out of memory.

    • The checkbox to enable GitHub Actions in the Management Console is now visible with any authentication method.

    • GitHub Actions could be enabled if the required storage was also configured.

    • ghe-repl-status could silently fail if MSSQL replication was not configured.

    • The format of several log files have changed, including the addition of a PID for different log types. This does not affect how GitHub Enterprise Support uses support bundles to troubleshoot issues.

    • A PATCH request to the webhook configuration API no longer erases the webhook secret.

    • Certain types of pre-receive hooks were failing.

  • On a freshly set up Servidor de GitHub Enterprise without any users, an attacker could create the first admin user.

  • Custom firewall rules are not maintained during an upgrade.

  • Git LFS tracked files uploaded through the web interface are incorrectly added directly to the repository.

  • When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.

  • When maintenance mode is enabled, some services continue to be listed as "active processes". The services identified are expected to run during maintenance mode. If you experience this issue and are unsure, contact GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) o GitHub Premium Support.

  • When GitHub Actions is enabled, use 'ghe-maintenance -u' to unset maintenance mode.

Enterprise Server 3.0.0.rc2

Release Candidate Download

January 29, 2021

Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the GitHub Blog or "About upgrades to new releases."

  • Fixes for known issues from Release Candidate 1

    • If you disabled GitHub Actions following an unsuccessful attempt to set up GitHub Actions, then you will not be able to create the first user and use the appliance.

    • The "Mandatory message viewed" audit log event was not being saved.

    • ghe-config-apply needed to run on a replica during an initial setup before ghe-repl-setup could run to start replication.

    • Removing yourself as an enterprise owner returned a 404.

  • Fixes for other issues

    • Issues with migrations and upgrades to 3.0.0 have been fixed.

    • Backup Utilities versioning now works for release candidate versions.

    • Generating a support bundle resulted in an error in the orchestrator logs.

    • A large restore could result in Redis running out of memory.

    • The checkbox to enable GitHub Actions in the Management Console is now visible with any authentication method.

    • GitHub Actions can only be enabled if the required storage is also configured.

    • ghe-repl-status could silently fail if MSSQL replication is not configured.

  • The known issues for Release Candidate 1 still apply, excluding the bug fixes listed.

Enterprise Server 3.0.0.rc1

Release Candidate Download

January 12, 2021

Release candidate versions should be tested on non-production environments. For more information about the Release Candidate Program, see the GitHub Blog or "About upgrades to new releases".

  • The format of several log files have changed, including the addition of a PID for different log types. This does not affect how GitHub Enterprise Support uses support bundles to troubleshoot issues.

  • A PATCH request to the webhook configuration API no longer erases the webhook secret.

  • On a freshly set up Servidor de GitHub Enterprise without any users, an attacker could create the first admin user.

  • Release Candidate 1 does not support Cluster mode.

  • Custom firewall rules are not maintained during an upgrade.

  • Git LFS tracked files uploaded through the web interface are incorrectly added directly to the repository.

  • When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.

  • Following an unsuccessful attempt to set up Actions, if you then disable Actions you will not be able to create the first user and use the appliance

  • The "Mandatory message viewed" audit log event is not being saved

  • ghe-config-apply must be run on a replica during first setup before ghe-repl-setup can be run to start replication.

  • Backup-utils can trigger unnecessary emails to administrators

  • Incorrect Packages settings are being displayed in the Organization member view page

  • After removing oneself as an Enterprise Owner, you are redirected to a 404 page. The operation is successful.

  • ghe-config-apply occassionally fails with ERROR: Failure waiting for nomad jobs to apply until the Nomad job queue is cleared. This currently requires as admin to delete /etc/nomad-jobs/queue.

  • When configuring a multiple replica node, the status of the replica can be incorrectly synchronized.

  • Customers attempting to restore a 3.0 backup to a new instance should not pre-configure the instance, as it may lead to a bad state for user logins. We recommend restoring to a fresh, unconfigured instance.

  • GitHub Enterprise Server 3.0 release candidates are not yet available in the Azure marketplace. To test release candidates in staging environments, start a 2.21 or 2.22 instance, and then upgrade it with the Azure upgrade package on the download page.

  • The image and upgrade package download size has increased. Customers on slow internet connections may find the packages take longer to download.