2.21

2.22 Release notes

3.0

Enterprise Server 2.22.10

Download

April 01, 2021

📣 This is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.

  • HIGH: An improper access control vulnerability was identified in GitHub Enterprise Server that allowed access tokens generated from a GitHub App's web authentication flow to read private repository metadata via the REST API without having been granted the appropriate permissions. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. The private repository metadata returned would be limited to repositories owned by the user the token identifies. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.4 and was fixed in versions 3.0.4, 2.22.10, 2.21.18. This vulnerability has been assigned CVE-2021-22865 and was reported via the GitHub Bug Bounty Program.

  • Packages have been updated to the latest security versions.

  • A timezone set on GitHub Enterprise 11.10.x or earlier was not being used by some services which were defaulting to UTC time.

  • Services were not transitioning to new log files as part of log rotation, resulting in increased disk usage.

  • The label on search results for internal repositories was shown as "Private" instead of "Internal".

  • On a freshly set up GitHub Enterprise Server 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.

  • Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.

  • 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.

Enterprise Server 2.22.9

Download

March 23, 2021

📣 This is not the latest patch release of this release series, and this is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.

Downloads have been disabled due to a major bug affecting multiple customers. A fix will be available in the next patch.

  • HIGH: A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to override environment variables leading to code execution on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.0.3 and was fixed in 3.0.3, 2.22.9, and 2.21.17. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22864.

  • Packages have been updated to the latest security versions.

  • Running ghe-cluster-config-init could cause a cluster to become inoperable.

  • Systemd could lose track of HAProxy's PID.

  • The mysql-failover warning was displayed indefinitely after a successful failover.

  • The ghe-cluster-config-init run was not fully accounting for the exit code of background jobs leading to improper handling of preflight checks.

  • A Security & Analysis link did not appear in the left-side navigation on the Settings page for repositories.

  • After disabling GitHub Packages, some organization pages would return an HTTP 500 error response.

  • Improves reliability of nomad services by implementing the same restart policy introduced in GitHub Enterprise Server 3.0.

  • Use a relative number for consul and nomad bootstrap_expect allowing for a cluster to bootstrap even if a handful of nodes are down.

  • Logs will rotate based on size in addition to time.

  • Added kafka-lite to the ghe-cluster-status command.

  • On a freshly set up GitHub Enterprise Server 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.

  • Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.

  • 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.

  • Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. To remedy and/or prevent this issue, run the following commands in the administrative shell (SSH), or contact GitHub Enterprise Support or GitHub Premium Support for assistance:

    printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate
    sudo /usr/sbin/logrotate -f /etc/logrotate.conf
    

Enterprise Server 2.22.8

Download

March 16, 2021

📣 This is not the latest patch release of this release series, and this is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.

  • Packages have been updated to the latest security versions.

  • Systemd journal logs were duplicated in multiple places.

  • A site admin could get a 500 error page while trying to view issues referenced from private repositories.

  • Importing of repository archives from GitHub Enterprise Server that are missing repository files would fail with an error.

  • On a freshly set up GitHub Enterprise Server 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.

  • Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.

  • 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.

  • Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the haproxy-cluster-proxy service. To determine if you have an affected instance:

    Single instance

    1. Run this in the administrative shell (SSH):

      if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi
      
    2. If it shows that there is a mismatch, reboot the instance.

    Cluster or High Availability configuration

    1. Run this in the administrative shell (SSH):

      ghe-cluster-each -- 'if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi'
      
    2. If it shows one or more nodes are affected, reboot the affected nodes.

Enterprise Server 2.22.7

Download

March 02, 2021

📣 This is not the latest patch release of this release series, and this is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.

  • HIGH: An improper access control vulnerability was identified in GitHub Enterprise Server that allowed authenticated users of the instance to gain write access to unauthorized repositories via specifically crafted pull requests and REST API requests. An attacker would need to be able to fork the targeted repository, a setting that is disabled by default for organization owned private repositories. Branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability has been assigned CVE-2021-22861. This issue was reported via the GitHub Bug Bounty Program.

  • HIGH: An improper access control vulnerability was identified in the GitHub Enterprise Server GraphQL API that allowed authenticated users of the instance to modify the maintainer collaboration permission of a pull request without proper authorization. By exploiting this vulnerability, an attacker would be able to gain access to head branches of pull requests opened on repositories of which they are a maintainer. Forking is disabled by default for organization owned private repositories and would prevent this vulnerability. Additionally, branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability has been assigned CVE-2021-22863. This issue was reported via the GitHub Bug Bounty Program.

  • HIGH: A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability has been assigned CVE-2020-10519 and was reported via the GitHub Bug Bounty Program.

  • MEDIUM: GitHub Tokens from GitHub Pages builds could end up in logs.

  • LOW: A specially crafted request to the SVN bridge could trigger a long wait before failure resulting in Denial of Service (DoS).

  • Packages have been updated to the latest security versions.

  • The load-balancer health checks in some cases could cause the babeld logs to fill up with errors about the PROXY protocol.

  • An informational message was unintentionally logged as an error during GitHub Enterprise Backup Utilities snapshots, which resulted in unnecessary emails being sent when backups were scheduled by cron jobs that listen for output to stderr.

  • While restoring a large backup, exception logging related to Redis memory exhaustion could cause the restore to fail due to a full disk.

  • When first setting up a new instance, if you selected "Configure as Replica" you would be unable to start replication.

  • When GitHub Actions was enabled, disabling maintenance mode in the management console failed.

  • When editing a wiki page a user could experience a 500 error when clicking the Save button.

  • An S/MIME signed commit using a certificate with multiple names in the subject alternative name would incorrectly show as "Unverified" in the commit badge.

  • Suspended user was sent emails when added to a team.

  • User saw 500 error when executing git operations on an instance configured with LDAP authentication.

  • The remove_org_member_package_access background job was visible in the management console and would continually increase.

  • When a repository had a large number of manifests an error You have reached the maximum number of allowed manifest files (20) for this repository. was shown on the Insights -> Dependency graph tab. For more information, see Visualization limits.

  • When uploading a new license file with a different number of seats from the previous license file, the seat difference was not correctly represented in the enterprise account Settings -> License page.

  • The "Prevent repository admins from changing anonymous Git read access" checkbox available in the enterprise account settings could not be successfully enabled or disabled.

  • When a GitHub Pages build failed, the email notification contained an incorrect link for support location.

  • During a leap year, the user was getting a 404 response when trying to view Contribution activity on a Monday.

  • On a freshly set up GitHub Enterprise Server 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.

  • Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.

  • 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.

  • Users may experience assets such as avatars not loading, or a failure to push/pull code. This may be caused by a PID mismatch in the haproxy-cluster-proxy service. To determine if you have an affected instance:

    Single instance

    1. Run this in the administrative shell (SSH):

      if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi
      
    2. If it shows that there is a mismatch, reboot the instance.

    Cluster or High Availability configuration

    1. Run this in the administrative shell (SSH):

      ghe-cluster-each -- 'if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi'
      
    2. If it shows one or more nodes are affected, reboot the affected nodes.

Enterprise Server 2.22.6

Download

December 17, 2020

📣 This is not the latest patch release of this release series, and this is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.

  • LOW: High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS).

  • Packages have been updated to the latest security versions.

  • Requests for some file resources like a zip archive or raw file could enter a redirection loop.

  • A timeout could prevent some Issues and Pull Requests searches from providing complete search results.

  • Custom tabs with non-alphabetic characters in small screens did not render correctly.

  • An underlying behavior was causing failures when pushing content to a Git LFS-enabled repository.

  • In some rare cases issues could cause a 500 error when accessed via the web interface.

  • On a freshly set up GitHub Enterprise Server 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.

  • Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.

  • 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.

Enterprise Server 2.22.5

Download

December 03, 2020

📣 This is not the latest patch release of this release series, and this is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.

  • Authorization service was being detected as unhealthy due to a race condition in the bootstrap which led to restart of the service.

  • The Elasticsearch upgrade process was not getting captured by ghe-diagnostics.

  • Enabling GitHub Actions on an upgraded high availability configuration caused errors in replication.

  • An underlying behavior was causing a service to become unavailable during the hotpatch upgrade process.

  • Users connecting to an active replica would get an error connecting to the live updates websocket.

  • A subset of log forwarding SSL certificates was not being applied correctly.

  • Email notifications sent to suspended users when they were removed from a Team or an Organization.

  • The way SSH certificates were applied between Organizations and Businesses was inconsistent.

  • When an account was rate limited due to using incorrect passwords, it could be locked out for up to 24 hours.

  • Pull request synchronization on repositories with many references could cause worker queues to fall behind.

  • When signing in with a local username and password (built-in authentication) after attempting to visit a specific page, the user was sent to the home page instead of their intended destination.

  • For GHES instances using built-in authentication with an internal SAML identity provider, users without an associated email address could not create a commit from the web interface.

  • On a freshly set up GitHub Enterprise Server 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.

  • Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.

  • 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.

Enterprise Server 2.22.4

Download

November 17, 2020

📣 This is not the latest patch release of this release series, and this is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.

  • Packages have been updated to the latest security versions.

  • The babeld logs were missing a separator between seconds and microseconds.

  • After upgrading GHES with a hotpatch, the ghe-actions-precheck and ghe-packages-precheck commands would fail with the error "docker load" accepts no arguments.

  • When the enterprise account "Repository visibility change" policy was set to "Enabled", organization owners could not change the visibility of repositories within the organization.

  • Audit logs could be attributed to 127.0.0.1 instead of the actual source IP address.

  • On a freshly set up GitHub Enterprise Server 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.

  • Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.

  • 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.

Enterprise Server 2.22.3

Download

November 03, 2020

📣 This is not the latest patch release of this release series, and this is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.

  • LOW: High CPU usage could be triggered by a specially crafted request to the SVN bridge resulting in Denial of Service (DoS) on the SVN bridge service. (updated 2020-11-16)

  • LOW: Incorrect token validation resulted in a reduced entropy for matching tokens during authentication. Analysis shows that in practice there's no significant security risk here.

  • Packages have been updated to the latest security versions.

  • GitHub Actions could fail to start up successfully if it was previously enabled on an instance running 2.22.0 and was upgraded to 2.22.1 or 2.22.2.

  • Configuration files for GitHub Actions were not copied to the replica when setting up high availability replicas potentially leading to errors during ghe-repl-promote.

  • On a freshly set up 2.22.1 or 2.22.2 instance or after upgrading to 2.22.1 or 2.22.2, the activity feed on an organization's dashboard would not update.

  • Editing issues templates with filenames containing non-ASCII characters would fail with a "500 Internal Server Error".

  • A metric gathering method for background jobs increased CPU utilization. (updated 2020-11-03)

  • On a freshly set up GitHub Enterprise Server 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.

  • Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.

  • 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.

  • Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address.

Enterprise Server 2.22.2

Download

October 20, 2020

📣 This is not the latest patch release of this release series, and this is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.

  • Packages have been updated to the latest security versions.

  • If the storage account settings failed to validate while configuring GitHub Actions, running ghe-actions-teardown was required before making a new attempt.

  • A custom proxy configuration could adversely affect the GitHub Actions environment.

  • On a change of an address on eth0, Nomad and Consul could get unresponsive.

  • When using self-signed certificates, GHES could have SSL validation exceptions upon configuring GitHub Actions.

  • Using a GitHub Action from a branch name with a + or / character resulted in an error: Unable to resolve action.

  • The enterprise account "Confirm two-factor requirement policy" messaging was incorrect.

  • On certain requests above 100MB, Kafka's buffer could be over-allocated.

  • On a freshly set up GitHub Enterprise Server 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.

  • Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.

  • 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.

  • GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.2. (updated 2020-10-23)

  • On a freshly set up 2.22.2 instance or after upgrading to 2.22.2, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27)

  • Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02)

Enterprise Server 2.22.1

Download

October 09, 2020

📣 This is not the latest patch release of this release series, and this is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.

  • MEDIUM: ImageMagick has been updated to address DSA-4715-1.

  • Requests from a GitHub App integration to refresh an OAuth access token would be accepted if sent with a different, valid OAuth client ID and client secret than was used to create the refresh token.

  • A user whose LDAP directory username standardizes to an existing GHES account login could authenticate into the existing account.

  • Packages have been updated to the latest security versions.

  • The NameID Format dropdown in the Management Console would be reset to "unspecified" after setting it to "persistent".

  • Upgrading using a hotpatch could fail with an error: 'libdbi1' was not found

  • Saving settings via the management console would append a newline to the TLS/SSL certificate and key files which triggered unnecessary reloading of some services.

  • System logs for Dependency Graph were not rotating, allowing unbounded storage growth.

  • The MS SQL Server performance graph showed statistics from the primary instance even when a replica was selected.

  • ghe-actions-precheck would silently exit without running the storage checks if Actions was not enabled.

  • Upgrade could fail if the resqued workers override setting is in use.

  • Some services running in containers were not sending logs to the journal.

  • Links to GitHub Security Advisories would use a URL with the hostname of the GitHub Enterprise Server instance instead of GitHub.com, directing the user to a nonexistent URL.

  • When importing a repository with ghe-migrator, an unexpected exception could occur when inconsistent data is present.

  • The enterprise account security settings page showed a "View your organizations' current configurations" link for the "Two-factor authentication" setting when the authentication mode in use does not support built in two-factor authentication.

  • OAuth refresh tokens would be removed prematurely.

  • Search repair tasks would generate exceptions during the migration phase of configuration.

  • On the settings page for GitHub Apps, the "Beta Features" tab was not visible in some circumstances.

  • When using ghe-migrator to import PR review requests, records associated with deleted users would result in extraneous database records.

  • When importing users with ghe-migrator, an error of "Emails is invalid" would occur if the system-generated email address were longer than 100 characters.

  • Logging webhook activity could use large amounts of disk space and cause the root disk to become full.

  • Users experienced slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node.

  • The repository Settings page of a repository for a user or organization GitHub Pages sites would fail with a "500 Internal Server Error".

  • Repository network maintenance operations could become stuck in a running state.

  • A repository being deleted immediately after uploading a code scanning result could cause a stall in the processing of code scanning results for all repositories.

  • When a large number of code scanning results were submitted at the same time, processing of batches could time out resulting in a stall in processing of code scanning results.

  • Creating a GitHub App from a manifest would fail.

  • GitHub usernames were changed unintentionally when using SAML authentication, when the GitHub username did not match the value of the attribute mapped to the username field in the Management Console.

  • Support is added for the AWS EC2 instance type m5.16xlarge.

  • Remove the requirement for SSH fingerprints in ghe-migrator archives as it can always be computed.

  • GitHub App Manifests now include the request_oauth_on_install field.

  • On a freshly set up GitHub Enterprise Server 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.

  • Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.

  • 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.

  • Configuration updates will fail when restoring data to a GitHub Actions-enabled instance if the original backup source did not have the feature enabled.

  • GitHub Actions can fail to start up successfully if it was previously enabled on an instance running 2.22.0 and is upgraded to 2.22.1. (updated 2020-10-23)

  • On a freshly set up 2.22.1 instance or after upgrading to 2.22.1, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27)

  • Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02)

Enterprise Server 2.22.0

Download

September 23, 2020

📣 This is not the latest patch release of this release series, and this is not the latest release of Enterprise Server. Please use the latest release for the latest security, performance, and bug fixes.

GitHub is excited to present GitHub Enterprise Server 2.22.0.

  • The stafftools page for viewing pending collaborator showed a 500 Internal Server Error when there was a pending email invite.

  • The Repository Health Check in stafftools could give incorrect results on busy repositories.

  • A logged in user trying to accept an email invitation could get a 404 Not Found error.

  • If a user navigated to a repository whose name started with "repositories.", they were redirected to the owner's "Repositories" tab instead of landing on the repository overview page.

  • Labels in the dashboard timeline did not have enough contrast.

  • On a freshly set up GitHub Enterprise Server 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.

  • Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.

  • 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.

  • The Name ID Format dropdown in the Management Console resets to "unspecified" after setting instance to "persistent".

  • The repository Settings page of a repository for a user or organization GitHub Pages sites will fail with a "500 Internal Server Error".

  • Users may experience slower Git clone and fetch performance on an instance with high availability replicas due to reads being forwarded to a different node.

  • Creating a GitHub App from a manifest fails. To work around this issue, users can follow the manual instructions for creating a GitHub App.

  • GitHub usernames may change unintentionally when using SAML authentication, if the GitHub username does not match the value of the attribute mapped to the username field in the Management Console. (updated 2020-10-08)

  • On a freshly set up 2.22.0 instance or after upgrading to 2.22.0, the activity feed on an organization's dashboard will no longer update. (updated 2020-10-27)

  • Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02)

Did this doc help you?

Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.