Skip to content

Commit 887b9ad

Browse files
sarahssarahs
authored
Merge pull request #19025 from github/late-april-patch-release-notes
GHES Patch Release Notes 3.0.6, 2.22.12, 2.21.20
2 parents 8ec4b00 + 0404ee7 commit 887b9ad

3 files changed

Lines changed: 68 additions & 0 deletions

File tree

‎data/release-notes/2-21/20.yml‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
date: '2021-04-28'
2+
sections:
3+
security_fixes:
4+
- Packages have been updated to the latest security versions.
5+
bugs:
6+
- Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover.
7+
- '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.'
8+
- Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected.
9+
- Organizations or projects with errors blocked migration and could not be excluded.
10+
changes:
11+
- Preflight checks allow all AWS instance types by default.
12+
known_issues:
13+
- On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
14+
- Custom firewall rules are not maintained during an upgrade.
15+
- 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.
16+
- 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.
17+
- 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.
18+
- Security alerts are not reported when pushing to a repository on the command line.

‎data/release-notes/2-22/12.yml‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
date: '2021-04-28'
2+
sections:
3+
security_fixes:
4+
- Packages have been updated to the latest security versions.
5+
bugs:
6+
- During upgrades, the process would pause indefinitely after `cleanup nomad job`.
7+
- 'Failing `ghe-cluster-failover` with the error message `Trilogy::Error: trilogy_connect`.'
8+
- '`ghe-cluster-status-mysql` showed warnings about failovers as errors.'
9+
- Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover.
10+
- '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.'
11+
- Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected.
12+
- Organizations or projects with errors blocked migration and could not be excluded.
13+
- Customers with more than three storage hosts were unable to restore to their disaster-recovery cluster due to the fullest disks being selected instead of empty nodes.
14+
changes:
15+
- Preflight checks allow all AWS instance types by default.
16+
known_issues:
17+
- On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
18+
- Custom firewall rules are not maintained during an upgrade.
19+
- 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.
20+
- 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.
21+
- 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.

‎data/release-notes/3-0/6.yml‎

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
date: '2021-04-28'
2+
sections:
3+
security_fixes:
4+
- Packages have been updated to the latest security versions.
5+
bugs:
6+
- During upgrades, the process would pause indefinitely after `cleanup nomad job`.
7+
- 'Failing `ghe-cluster-failover` with the error message `Trilogy::Error: trilogy_connect`.'
8+
- '`ghe-cluster-status-mysql` showed warnings about failovers as errors.'
9+
- Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover.
10+
- Upgrades did not include the latest version of Actions runner properly installed.
11+
- '`github-env` configuration could result in zombie processes.'
12+
- '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.'
13+
- Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected.
14+
- Organizations or projects with errors blocked migration and could not be excluded.
15+
- The Create Repository button was disabled for users who belonged to more than 50 organizations.
16+
- Deleting a branch would temporarily flash an error message indicating something went wrong when the deletion was successful.
17+
- The `rms-packages` index was shown in the site admin dashboard.
18+
- Organization owner was unable to create internal repository due to the correct visibility options not being displayed on the form.
19+
- The repository actions tab rendered a 500 in cases where the actions starter workflows were misconfigured.
20+
- Customers with more than three storage hosts were unable to restore to their disaster-recovery cluster due to the fullest disks being selected instead of empty nodes.
21+
- Code Scanning backend services did not start up reliably after applying hotpatches.
22+
changes:
23+
- Preflight checks allow all AWS instance types by default.
24+
known_issues:
25+
- On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
26+
- Custom firewall rules are not maintained during an upgrade.
27+
- 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.
28+
- 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.
29+
- 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.

0 commit comments

Comments
 (0)