f6027a3fab
* remove RC banner * archive RC release notes * move it all over * add xenserver deprecation warning * Remove the check annotations known issue as it no longer applies * Copied in my release notes from the spreadsheet, pending a couple more * Add security release note * Add changes field * Fix spokesd linter warning * Add quotes around the second changes bullet * update with code scanning retraction * move bug fixes around * npm lint changes * more lint checks * update with bug fix * reorganize a bit * update typo * add a few more edits * update with mobile beta filtering * fix formatting problems * quotes * update to fix linting errors * Update data/release-notes/enterprise-server/3-1/0.yml * update with @lucascosti's amazing feedback * move security fixes out of changes * pull out security fixes * typo in security section * move security fixes down * Add the last two known bugfixes to the bugs section * Adding known issue and rewriting a bug fix * Adding known issue around using ghe-repo owner/reponame Co-authored-by: Zachary Mark <zachary-mark@github.com> Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> Co-authored-by: Melanie Yarbrough <11952755+myarb@users.noreply.github.com> Co-authored-by: Mike Surowiec <mikesurowiec@users.noreply.github.com> Co-authored-by: Amy Burns <timeyoutakeit@github.com>
21 lines
1.8 KiB
YAML
21 lines
1.8 KiB
YAML
date: '2021-05-06'
|
|
release_candidate: true
|
|
deprecated: true
|
|
intro: If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments.
|
|
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:
|
|
- 'A scheduled cleanup job can cause performance to degrade on an instance with a very large `check_annotations` table.'
|
|
changes:
|
|
- Check annotations older than 4 months will be archived.
|
|
- 'The `firstPatchedVersion` field is now available on `SecurityVulnerability` objects in the GraphQL API.'
|
|
known_issues:
|
|
- The GitHub Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance 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.
|