Release v13.20.0

See merge request gitlab-org/gitlab-shell!492

Fix the Geo SSH push proxy hanging

See merge request gitlab-org/gitlab-shell!487

Remove bin/authorized_keys

See merge request gitlab-org/gitlab-shell!491

Add a make install command

Closes #475

See merge request gitlab-org/gitlab-shell!490

Changelog: added

We committed to removing this script in the 13.x release cycle, and it
was announced then, but we never actually got around to it.

Its functionality is completely replicated, in a safer manner, by the
bin/gitlab-shell-authorized-keys script.

Changelog: removed

Geo SSH proxy push currently impossible when the only
action that happens is branch removal. This fix
works in a way that it waits for flush packet from git
and then checks pkt lines to determine is pack data is expected.
The thing is that git doesnt send pack data when only
branch removal happens. Explanation is in
https://gitlab.com/gitlab-org/gitlab/-/issues/330494

Fix a failing spec

See merge request gitlab-org/gitlab-shell!489

When the shell environment includes SSH_CONNECTION, one spec fails as
the way we're stubbing the environment to the subprocess doesn't wipe
out the pre-existing variable. This commit changes how we do it so the
spec passes even in this environment.

Create PROCESS.md page with Security release process

See merge request gitlab-org/gitlab-shell!488

Standardize logging timestamp format

Closes #140

See merge request gitlab-org/gitlab-shell!485

"Limits" to "Limit" on line 10 to align tenses

See merge request gitlab-org/gitlab-shell!483

Release v13.19.0

See merge request gitlab-org/gitlab-shell!482

Add acceptance test for git-upload-pack

See merge request gitlab-org/gitlab-shell!477

fix: upgrade of the gitaly dependency

See merge request gitlab-org/gitlab-shell!481

Gitaly project now properly respects module release flow
and includes a module suffix in the package name. It requires
to re-write all non-suffixed imports with suffixed of a specific
version of tha module. With proper module versioning we don't
need to use a 'replace' directive to point to specific commit
and can use semantic versioning for the gitaly dependency.

Part of: https://gitlab.com/gitlab-org/gitaly/-/issues/3177

Unit test wrong channel type

See merge request gitlab-org/gitlab-shell!479

Contributes to https://gitlab.com/gitlab-org/gitlab-shell/-/issues/500

Add acceptance test for git-upload-archive

See merge request gitlab-org/gitlab-shell!478

Contributes to https://gitlab.com/gitlab-org/gitlab-shell/-/issues/500

Fix opentracing setup for gitlab-sshd

Closes #501

See merge request gitlab-org/gitlab-shell!473

Add first Gitaly acceptance test

See merge request gitlab-org/gitlab-shell!475

fix: upgrade of the labkit dependency

See merge request gitlab-org/gitlab-shell!474

The labkit has a fix in the dependency chain b36f912 (Merge branch 'ps-fix-dep-version' into 'master', 2021-05-20).

1.4.0 has introduced the format change
Since v1 means latest 1.* image, we're pulling the unsupported version

Acceptance tests for 2fa_recovery_codes, 2fa_verify, and git-lfs-authenticate

See merge request gitlab-org/gitlab-shell!472

Previously, opentracing (if configured) was initialized late in the
gitlab-shell process's lifespan, coming just before making a gRPC
call to Gitaly.

By moving the opentracing initialization to be at process startup, we
make it available for the whole process lifecycle, which is very useful
to gitlab-sshd, as it means we'll only call tracing.Initialize() once
on process startup, rather than once per SSH connection.

To get this working, we need to introduce a context to gitlab-sshd.
This carries the client/service name, but also carries an initial
correlation ID. The main outcome of this is that all calls to the
authorized_keys endpoint from a given gitlab-sshd process will now
share a correlation ID. I don't have a strong opinion about this either
way.

Changelog: fixed

Add acceptance test for personal_access_token command

See merge request gitlab-org/gitlab-shell!471