GitHub Enterprise - The best way to build and ship software

COLLECTED BY

Organization: Archive Team

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.

The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.

This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.

Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.

The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.

Collection: ArchiveBot: The Archive Team Crowdsourced Crawler

ArchiveBot is an IRC bot designed to automate the archival of smaller websites (e.g. up to a few hundred thousand URLs). You give it a URL to start at, and it grabs all content under that URL, records it in a WARC, and then uploads that WARC to ArchiveTeam servers for eventual injection into the Internet Archive (or other archive sites).

To use ArchiveBot, drop by #archivebot on EFNet. To interact with ArchiveBot, you issue commands by typing it into the channel. Note you will need channel operator permissions in order to issue archiving jobs. The dashboard shows the sites being downloaded currently.

There is a dashboard running for the archivebot process at http://www.archivebot.com.

ArchiveBot's source code can be found at https://github.com/ArchiveTeam/ArchiveBot.

TIMESTAMPS

GitHub Enterprise 2.22.1 October 09, 2020 Download

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

Bug Fixes

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.

Changes

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.

Known Issues

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.

Thanks!

The GitHub Team

GitHub Enterprise 2.22.0 September 23, 2020 Download

GitHub is excited to present GitHub Enterprise Server 2.22.0.

New Beta Features

GitHub Actions Beta

GitHub Actions is a powerful, flexible solution for CI/CD and workflow automation. GitHub Actions on Enteprise Server includes tools to help you manage the service, including key metrics in the Management Console, audit logs and access controls to help you control the roll out.

You will need to provide your own storage and runners for GitHub Actions. AWS S3, Azure Blob Storage and MinIO are supported. Please review the updated minimum requirements for your platform before you turn on GitHub Actions. To learn more, contact the GitHub Sales team or sign up for the beta.

GitHub Packages Beta

GitHub Packages 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 GitHub Packages. To learn more, contact the GitHub Sales team or sign up for the beta.

Advanced Security Code Scanning Beta

GitHub Advanced Security code scanning is a developer-first, GitHub-native static application security testing (SAST). Easily find security vulnerabilities before they reach production, all powered by the world’s most powerful code analysis engine: CodeQL.

Administrators using GitHub Advanced Security can sign up for and enable GitHub Advanced Security code scanning beta. Please review the updated minimum requirements for your platform before you turn on GitHub Advanced Security code scanning.

Features

Pull Request Retargeting

When a pull request's head branch is merged and deleted, all other open pull requests in the same repository that target this branch are now retargeted to the merged pull request's base branch. Previously these pull requests were closed.

Suspend and Unsuspend an App Installation

Administrators and users can suspend any GitHub App’s access for as long as needed, and unsuspend the app on command through Settings and the API. Suspended apps cannot access the GitHub API or webhook events. You can use this instead of uninstalling an application, which deauthorises every user.

Improved Large Scale Performance

We have revised the approach we take to scheduling network maintenance for repositories, ensuring large monorepos are able to avoid failure states.

Passive replicas are now supported and configurable on GitHub Enterprise Server cluster deployments. These changes will enable faster failover, reducing RTO and RPO.

View All of Your Users

For exceptionally large teams, administrators can adjust the 1,500 default maximum for user lists.

Changes

Administration Changes

Shared workers have been enabled to make live updates more resilient by sharing connections across tabs.
The "Contact Support" link on 50x error pages now links to the support email or link configured in the Management Console.
It's now possible to manage global announcements and expiration dates through the enterprise account settings.
You can now exempt certain users from the default API rate limits configured in the management console, if necessary.
Repository administrators can now set their repository to any available visibility option from a single dialog in the repository's settings. Previously, you had to navigate separate sections, buttons, and dialog boxes for changing between public and private and between private and internal.
A new Enterprise settings link on the user dropdown menu makes it easier to navigate to Enterprise Account Settings.
The legacy "Admin Center" link on the /stafftools page has been removed. The "Enterprise" link is now the best way to navigate to the Enterprise Account from the /stafftools page.
The Options sub-menu item in the Enterprise Account settings has been moved from the Settings section to the Policies section.
Accessing resources by using a personal access token or SSH key now counts as user activity. This relieves administrators from the burden of filtering out certain users from the user dormancy reports and makes it safer to use the "Suspend all" button without accidentally suspending users who only accessed GitHub in a read-only way over the APIs with a Personal Access Token (PAT) or SSH key.

Security Changes

Two-factor recovery codes can no longer be used during the two-factor sign in process. One-Time-Passwords are the only acceptable values.
When a user is signed into GitHub Enterprise Server through single sign-on, the default repository visibility selection is Private.
Owners of GitHub Apps can now choose to have their user-to-server access tokens expire after 8 hours, to help enforce regular token rotation and reduce the impact of a compromised token.

Developer Changes

The GitHub UI has undergone a design refresh, and the repositories homepage has been redesigned, including a responsive layout and improved mobile web experience.
In the "Clone with SSH" repository dropdown menu, users will now be notified if they do not have any keys setup.
Commits are now ordered chronologically in the pull request timeline and commits tab. This new ordering is also reflected in the "List commits on a pull request" REST API and GraphQL "PullRequest object" timeline connection.
Users can now set a skin tone default for emoji autocomplete results in comment text areas.
Tree-sitter improves syntax highlighting and is now the default library used for language parsing.

Users and organizations can add Twitter usernames to their GitHub profiles

Developers and organizations can now add their Twitter username to their profile

API Changes

Graduated Previews

The following previews are now an official part of the API:

The GitHub Apps API and endpoints that returned the performed_via_github_app property no longer require the machine-man preview header.
To add and view a lock reason to an issue, you no longer need to use the sailor-v preview header.

GraphQL Schema Changes

The GraphQL schema changes include backwards-compatible changes, schema previews, and upcoming breaking changes.

Bug Fixes

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.

Deprecations

Upcoming Deprecation of GitHub Enterprise Server 2.19

GitHub Enterprise Server 2.19 will be deprecated as of November 12, 2020 That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, upgrade to the newest version of GitHub Enterprise Server as soon as possible.

Deprecation of Legacy GitHub App Webhook Events

Starting with GitHub Enterprise Server 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in GitHub Enterprise Server 2.25.0. The deprecated events integration_installation and integration_installation_repositories have equivalent events which will be supported. More information is available in the deprecation announcement blog post.

Deprecation of Legacy GitHub Apps Endpoint

Starting with GitHub Enterprise Server 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in GitHub Enterprise Server 2.25.0. More information is available in the deprecation announcement blog post.

Deprecation of OAuth Application API

GitHub no longer supports the OAuth application endpoints and have replaced them with a version that moves the access token to the request body for improved security. Brownouts will start in March 2021 and all calls to the old version of the OAuth application endpoints will return a status code of 404 starting on May 5, 2021 at 16:00 UTC.

Backups and Disaster Recovery

GitHub Enterprise Server 2.22 requires at least GitHub Enterprise Backup Utilities 2.22.0 for Backups and Disaster Recovery.

Known Issues

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)

Thanks!

The GitHub Team

Sep	OCT	Nov
	19
2019	2020	2021

Release notes for the 2.22 series

GitHub Enterprise 2.22.1 October 09, 2020 Download

Security Fixes

Bug Fixes

Changes

Known Issues

GitHub Enterprise 2.22.0 September 23, 2020 Download

New Beta Features

GitHub Actions Beta

GitHub Packages Beta

Advanced Security Code Scanning Beta

Features

Pull Request Retargeting

Suspend and Unsuspend an App Installation

Improved Large Scale Performance

View All of Your Users

Changes

Administration Changes

Security Changes

Developer Changes

Users and organizations can add Twitter usernames to their GitHub profiles

API Changes

Graduated Previews

GraphQL Schema Changes

Bug Fixes

Deprecations

Upcoming Deprecation of GitHub Enterprise Server 2.19

Deprecation of Legacy GitHub App Webhook Events

Deprecation of Legacy GitHub Apps Endpoint

Deprecation of OAuth Application API

Backups and Disaster Recovery

Known Issues