We will remove the foreign key in a later MR but for now we can start
with adding the LFK. These have all been determined as safe to be
converted to a loose foreign key in
https://gitlab.com/gitlab-org/gitlab/-/issues/348269 .

Do not show participants invisible to the user

See merge request gitlab-org/gitlab!77021

It is called here documents

See merge request gitlab-org/gitlab!77599

Add solution section

See merge request gitlab-org/gitlab!77572

Externalize strings for translation in todos template

See merge request gitlab-org/gitlab!77402

Changelog: fixed

Geo: adapt verification timed out query to use state table

See merge request gitlab-org/gitlab!77364

Fix broken link in default ReadME

See merge request gitlab-org/gitlab!77026

Merge branch '341195-reschedule-pending-recalculatevulnerabilitiesoccurrencesuuid-jobs' into 'master'

Recalculate UUID for all Vulnerability::Finding records, attempt 2

See merge request gitlab-org/gitlab!75546

There are two major reasons for this:

1. We made a mistake in the algorithm when recalculating this for the
first time.
See: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/67578

2. The algorithm changed yet again to improve the tracking method
See: https://gitlab.com/gitlab-org/gitlab/-/issues/322044

Changes:

* Update background migration to use signatures

* Make previous reschedule a no-op so customers doing major version
  leaps will not schedule the same job multiple times

* Remove ALL jobs from `background_migration_jobs` table. Succeeded jobs
  should be removed anyway and pending jobs were not finished because we
  had records for which the recalculation yielded identical UUIDv5. The
  reason we had such records was due to mistake outlined in point 1.
  This situation was fixed by
  https://gitlab.com/gitlab-org/gitlab/-/merge_requests/74008

* Schedule `RecalculateVulnerabilitiesOccurrencesUuid` over entire
  `vulnerability_occurrences` table so we can leverage our new algorithm
  and finish the migration path from UUIDv4 to UUIDv5.

Changelog: added

Adding resolution to common error message

See merge request gitlab-org/gitlab!77390

Add terraform_module to  package_type values

See merge request gitlab-org/gitlab!77299

Remove `resources :user_callouts` from `config/routes.rb`

See merge request gitlab-org/gitlab!77033

Update Package Next Steps after install

See merge request gitlab-org/gitlab!77522

Rate limit update username action

See merge request gitlab-org/gitlab!77221

ci: Skip flaky tests automatically and allow to opt-out

See merge request gitlab-org/gitlab!77329

Add migrate local data to object storage steps for consolidated form

See merge request gitlab-org/gitlab!77468

Fix 347168

Updated Vale to use latest Readability extension

See merge request gitlab-org/gitlab!77531

Updated title to try to clarify that it's about development

See merge request gitlab-org/gitlab!77541

Refactoring FileRegistryRemoval service  and specs

See merge request gitlab-org/gitlab!77539

It refactors FileRegistryRemoval but mostly we optimized
its spec

Match address of host when checking whether to login

See merge request gitlab-org/gitlab!73492

* Makes sure we are on the login page of the desired host before
  deciding whether we need to re-login. Currently only checks if we're
  on the login page. For Geo specs, we need to sign into different hosts

Changelog: fixed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/73492
EE: true

Add createdAt to Runner GraphQL API

See merge request gitlab-org/gitlab!77561

Improve LFS client performance and fix compatibility with Azure DevOps

See merge request gitlab-org/gitlab!77326

Make navigation themes translatable

See merge request gitlab-org/gitlab!77483

Changelog: changed

Mention that this doc is about the minimum requirements

See merge request gitlab-org/gitlab!77596

Minor content edit

Updated SBOM Survey Banner Heading

See merge request gitlab-org/gitlab!77588

The LFS client that is used in repository mirroring had a few
shortcomings:

1. Chunked transfers were never used because the Content-Length was
always specified. We now only including Content-Length if chunked
encodings are not requested.

2. Azure DevOps passes in the username in the upload URL, but this cause
HTTParty to serialize this in the Authorization header instead of using
the mirror credentials. We now strip the URL of username/passwords if
HTTP Basic Auth is used.

Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/340482

Changelog: fixed

Backfill Escalation Statuses for Incident issues

See merge request gitlab-org/gitlab!76714

Squash and merge page - CTRT revisions

See merge request gitlab-org/gitlab!77452