jprdonnelly/docs
1
0
Fork 0
mirror of synced 2026-01-30 06:01:34 -05:00
Code Issues Projects Releases Wiki Activity

Merge pull request #19530 from github/late-may-patch-release

Browse Source 
Patch release notes for 2.21.22, 2.22.14, 3.0.8
This commit is contained in:
Sarah Schneider
2021-05-25 12:06:06 -04:00
committed by GitHub
parent 4d35716afb 7d75a2d533
commit 9cd67592d7
3 changed files with 56 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
data/release-notes/2-21/22.yml Normal file
View File

@@ -0,0 +1,15 @@
date: '2021-05-25'
sections:
security_fixes:
- '**MEDIUM:** Under certain circumstances, users who were removed from a team or organization could retain write access to branches they had existing pull requests opened for.'
- Packages have been updated to the latest security versions.
bugs:
- An IP address added by an admin using the "Create Whitelist Entry" button could still be locked out.
- In a cluster or HA environment, GitHub Pages builds could be triggered on secondary nodes where they would fail.
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](https://github.com/blog/2105-upload-files-to-your-repositories) 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.
- Security alerts are not reported when pushing to a repository on the command line.

17
data/release-notes/2-22/14.yml Normal file
View File

@@ -0,0 +1,17 @@
date: '2021-05-25'
sections:
security_fixes:
- '**MEDIUM:** Under certain circumstances, users who were removed from a team or organization could retain write access to branches they had existing pull requests opened for.'
- Packages have been updated to the latest security versions.
bugs:
- Normal replication delays in MSSQL generated warnings.
- An IP address added by an admin using the "Create Whitelist Entry" button could still be locked out.
- '`spokesd` created excessive log entries including the phrase "fixing placement skipped".'
changes:
- Check annotations older than 4 months will be archived.
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](https://github.com/blog/2105-upload-files-to-your-repositories) 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.

24
data/release-notes/3-0/8.yml Normal file
View File

@@ -0,0 +1,24 @@
date: '2021-05-25'
sections:
security_fixes:
- '**MEDIUM:** Under certain circumstances, users who were removed from a team or organization could retain write access to branches they had existing pull requests opened for.'
- Packages have been updated to the latest security versions.
bugs:
- On the "Configure Actions and Packages" page of the initial installation process, when an admin clicked the "Test domain settings" button the test did not complete.
- Running `ghe-btop` failed with error `cannot find a 'babeld' container`.
- Users were experiencing service unavailability after upgrading due to a mismatch of internal and external timeout values.
- Normal replication delays in MSSQL generated warnings.
- Link for GitHub Enterprise Clustering Guide on management console was incorrect.
- An IP address added by an admin using the "Create Whitelist Entry" button could still be locked out.
- References to the "Dependency graph" and "Dependabot alerts" features were shown on repositories where they were not enabled.
- HTTP POST requests to the `/hooks` endpoint could fail with a 401 response due to the `hookID` being set incorrectly.
- The `build-server` process failed to clean up processes leaving them in the `defunct` state.
- '`spokesd` created excessive log entries including the phrase "fixing placement skipped".'
changes:
- Check annotations older than 4 months will be archived.
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](https://github.com/blog/2105-upload-files-to-your-repositories) 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.