Update GitLab Shell to v13.21.0
What does this MR do?
We're overdue releasing a set of gitlab-shell changes. In particular, this release contains many improvements to gitlab-sshd, but there are also some community contributions. More details in the gitlab-shell release MR: gitlab-shell!512 (merged)
There was some oddness around the security release - we upgraded to v13.20.0, then got downgraded back to v13.19.1 afterwards
I've verified that the security release commits are in v13.21.0 (they aren't in v13.20.0, and there was never a v13.20.1).
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Edited by Nick Thomas