Update dependency @gitlab/svgs to ^1.63.0

See merge request gitlab-org/gitlab-ce!28715

Throw an error when formatDate's input is invalid

See merge request gitlab-org/gitlab-ce!28713

Resolve CE/EE diffs in project members

Closes gitlab-ee#10496

See merge request gitlab-org/gitlab-ce!28550

Externalize strings of preferences page in user profile

See merge request gitlab-org/gitlab-ce!28746

Append endline only if suggestion present

Closes #58566

See merge request gitlab-org/gitlab-ce!28703

Before this fix, a suggestion which just removes
an empty line wasn't appliable

Externalize stirngs of Authentication log page in user profile

See merge request gitlab-org/gitlab-ce!28750

protected should be Boolean type

See merge request gitlab-org/gitlab-ce!28766

Add expand/collapse button to operation settings

Closes #61511

See merge request gitlab-org/gitlab-ce!28620

Add ability to expand/collapse operation settings

Docs: Remove stray full stop from the middle of the sentence

See merge request gitlab-org/gitlab-ce!28403

Update order of list to match HA setup order

See merge request gitlab-org/gitlab-ce!28429

Improve performance of jobs controller show

Closes #60708

See merge request gitlab-org/gitlab-ce!28093

Merge branch '28996-automatic-https-certificate-creation-renewal-for-pages-custom-domains-4' into 'master'

Store Let's Encrypt private_key in `application_settings` instead of `secrets.yml`

See merge request gitlab-org/gitlab-ce!28353

Storing this key in secrets.yml was a bad idea,
it would require users using HA setups to manually
replicate secrets across nodes during update,
it also needed support from omnibus package

* Revert "Generate Let's Encrypt private key"
  This reverts commit 444959bf.

* Add Let's Encrypt private key to settings
  as encrypted attribute

* Generate Let's Encrypt private key
  in database migration

Group SAML docs explain GitLab.com SSO sign in

See merge request gitlab-org/gitlab-ce!28699

Updates documentation to reflect that SAML can now
be used to sign into the GitLab instance, instead of
just updating group membership.

fix relationship typo

See merge request gitlab-org/gitlab-ce!28797

add postgres version to subsequent helm deploys

See merge request gitlab-org/gitlab-ce!28735

If the postgres image version isn't passed to upgrades, helm will revert to the default postgres version. If it crosses incompatible version boundaries, this will break postgres horribly, as it won't be able to read the data files.

As documented in
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/api/project_level_variables.md#create-variable
and it's a boolean in `db/schema.rb`

Merge branch '11609-geo-remove-support-for-using-geo-with-an-installation-from-source-docs' into 'master'

Geo - Remove support for using Geo with an installation from source

Closes gitlab-ee#11609

See merge request gitlab-org/gitlab-ce!28737

Docs: add tip for Kubernetes executor using dind

Closes #61881

See merge request gitlab-org/gitlab-ce!28457

Add documentation for frontend fixtures

Closes #59973

See merge request gitlab-org/gitlab-ce!28541

Migrate the monitoring dashboard store to vuex

See merge request gitlab-org/gitlab-ce!28555

This changes the monitoring javascript store from
an object based to a vuex one

Update GitLab Runner Helm Chart to 0.5.1/11.11.1

See merge request gitlab-org/gitlab-ce!28720

Disable two_step_rebase feature flag

See merge request gitlab-org/gitlab-ce!28778

Disabling because of https://gitlab.com/gitlab-org/gitlab-ce/issues/62353

Remove `docker pull` prefix when copying a tag from the registry

Closes #46660

See merge request gitlab-org/gitlab-ce!28757

Update changelogs/unreleased/28757-remove-docker-pull-prefix-when-copying-a-tag-from-the-registry.yml

Using Geo with source-based installs was deprecated in GitLab 11.5.

This commit removes this support now that the deprecation notice has
been in place for quite a few releases.

Part of single codebase changes.