# Conflicts:
#   internal/command/twofactorverify/twofactorverify.go

Fix connections duration metrics

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

Update Version File

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

ci: start integrating go 1.18 into the CI pipelines

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

We need to pass time.Now as a param, otherwise it's calculated on call

Improve login grace timeout message

Closes #553

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

Abort long-running unauthenticated SSH connections

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

Use gitlab-dangerfiles to improve MR hygiene

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

Release 13.24.2

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

- Bump gitaly client !584

Bump gitaly client

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

Bump gitaly client to 51da8bc17059e4ccd39873e4f3def935341472b8 to get
changes from
https://gitlab.com/gitlab-org/gitaly/-/merge_requests/4439.

Signed-off-by: Rémy Coutable <remy@rymai.me>

Add docs for grace-period and probes config options

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

Release 13.24.1

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

Reuse Gitaly connections and sidechannel

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

Default to info level for an empty log-level

Closes #550

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

I'd assumed that the `omitempty` directive for LogLevel in
internal/config/config.go would get us this behaviour. If it did, we
wouldn't have had to specify the default twice. Unfortunately, it
doesn't, which is to say that given a config file like:

```
log_level:
```

The default *is* overridden by the empty string.

It's an easy enough fix.

Changelog: fixed

When gitlab-sshd has been introduced we've started running our
own SSH server. In this case we're able to cache and reuse
Gitaly connections and Registry.

It helps to reduce memory usage.

Update Gitaly dependency to v14.9.0-rc1

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