diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-07-23 21:27:09 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-07-23 21:27:09 +0300 |
| commit | bcc70301531b6c3118120173389f2aaa7452bf11 (patch) | |
| tree | 161f1ee56e15ec9e59f48c5e1a9cb86b62469a49 /doc/update | |
| parent | d47fc5085a706ab37d038636c9d5934da69853f0 (diff) | |
Add latest changes from gitlab-org/gitlab@13-2-stable-ee
Diffstat (limited to 'doc/update')
| -rw-r--r-- | doc/update/README.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/update/README.md b/doc/update/README.md index 26e52229fd2..fa9fdee4ed4 100644 --- a/doc/update/README.md +++ b/doc/update/README.md @@ -227,6 +227,12 @@ GitLab installations that have multiple web nodes will need to be [upgraded to 13.1](#1310) before upgrading to 13.2 (and later) due to a breaking change in Rails that can result in authorization issues. +GitLab 13.2.0 [remediates](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/35492) an [email verification bypass](https://about.gitlab.com/releases/2020/05/27/security-release-13-0-1-released/). +After upgrading, if some of your users are unexpectedly encountering 404 or 422 errors when signing in, +or "blocked" messages when using the command line, +their accounts may have been un-confirmed. +In that case, please ask them to check their email for a re-confirmation link. + ### 13.1.0 In 13.1.0, you must upgrade to either: |