SSH access stop working after upgrade to gitlab shell 13.21.1 on arch linux

Summary

SSH access, like git clone, git push stop working after migration my gitlab on-promise to new version gitlab 14.3.0-1 (arch system).

Steps to reproduce

I have problem after migration of my on-promise gitlab to new version gitlab 14.3.0-1 (arch package). The SSH access is stop working. Https works. I tried to test ssh

  ssh -Tv gitlab@server-ip

(gitlab name is default in arch config, not git and it works normally before update)

There is shown this potential problem:

  debug1: Remote: /var/lib/gitlab/.ssh/authorized_keys:1: key options: command user-rc
  debug1: Remote: /var/lib/gitlab/.ssh/authorized_keys:1: key options: command user-rc
  remote:
  remote: ========================================================================
  remote:
  remote: Failed to get username: who='' is invalid
  remote:
  remote: ========================================================================
  remote:
  debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
  debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0

Is it correct? Or I have to find the problem in another place of configuration? Git access with SSH with user "gitlab" doesn't work anymore (it means git pull, git clone etc).

Results of GitLab application Check

System information
System:		
Current User:	gitlab
Using RVM:	no
Ruby Version:	3.0.2p107
Gem Version:	/usr/lib/ruby/2.7.0/bundler/spec_set.rb:86:in `block in materialize': Could not find rake-13.0.6 in any of the sources (Bundler::GemNotFound)
	from /usr/lib/ruby/2.7.0/bundler/spec_set.rb:80:in `map!'
	from /usr/lib/ruby/2.7.0/bundler/spec_set.rb:80:in `materialize'
	from /usr/lib/ruby/2.7.0/bundler/definition.rb:170:in `specs'
	from /usr/lib/ruby/2.7.0/bundler/definition.rb:237:in `specs_for'
	from /usr/lib/ruby/2.7.0/bundler/definition.rb:226:in `requested_specs'
	from /usr/lib/ruby/2.7.0/bundler/runtime.rb:101:in `block in definition_method'
	from /usr/lib/ruby/2.7.0/bundler/runtime.rb:20:in `setup'
	from /usr/lib/ruby/2.7.0/bundler.rb:149:in `setup'
	from /usr/lib/ruby/2.7.0/bundler/setup.rb:20:in `block in <top (required)>'
	from /usr/lib/ruby/2.7.0/bundler/ui/shell.rb:136:in `with_level'
	from /usr/lib/ruby/2.7.0/bundler/ui/shell.rb:88:in `silence'
	from /usr/lib/ruby/2.7.0/bundler/setup.rb:20:in `<top (required)>'
	from <internal:/usr/lib/ruby/3.0.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
	from <internal:/usr/lib/ruby/3.0.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
Bundler Version:2.7.0
Rake Version:	13.0.6
Redis Version:	6.2.5
Git Version:	2.33.0
Sidekiq Version:5.2.9
Go Version:	go1.17.1 linux/amd64

GitLab information
Version:	14.3.0
Revision:	ceec8accb09
Directory:	/usr/share/webapps/gitlab
DB Adapter:	PostgreSQL
DB Version:	13.3
URL:		https://gitlab.domain.com
HTTP Clone URL:	https://gitlab.domain.com/some-group/some-project.git
SSH Clone URL:	gitlab@gitlab.domain.com:some-group/some-project.git
Using LDAP:	no
Using Omniauth:	yes
Omniauth Providers:

GitLab Shell
Version:	13.21.1
Repository storage paths:
- default: 	/var/lib/gitlab/repositories
GitLab Shell path:		/usr/share/webapps/gitlab-shell
Git:		/usr/bin/git

Check result: check pass correctly too. There is no issue.

Workaround

Downgrade to gitlab-shell 13.20.0

Edited by Kenneth Chu