1580e6be4f
* add release notes for 2.21.23, 2.22.15, 3.0.9, and 3.1.1 * add known issue for Actions after upgrade to 3.1 * Update data/release-notes/enterprise-server/2-21/23.yml Co-authored-by: Martin Lopes <martin389@github.com> * Apply suggestions from code review Co-authored-by: Martin Lopes <martin389@github.com> Co-authored-by: Martin Lopes <martin389@github.com> Co-authored-by: Melanie Yarbrough <11952755+myarb@users.noreply.github.com>
16 lines
1.4 KiB
YAML
16 lines
1.4 KiB
YAML
date: '2021-06-10'
|
|
sections:
|
|
security_fixes:
|
|
- Packages have been updated to the latest security versions.
|
|
bugs:
|
|
- Import failures of organizations or repositories from non-GitHub sources could produce an `undefined method '[]' for nil:NilClass` error.
|
|
changes:
|
|
- Users of the GraphQL API can query the public field `closingIssuesReferences` on the `PullRequest` object. This field retrieves issues that will be automatically closed when the related pull request is merged. This approach will also allow this data to be migrated in future, as part of a higher fidelity migration process.
|
|
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 removed during the upgrade process.
|
|
- 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 blob's 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.
|