Backfill / update timelogs.spent_at where NULL

See merge request gitlab-org/gitlab!76844

Docs: Minor fixes Configure docs

See merge request gitlab-org/gitlab!77061

Add sca notice to container scanning docs

See merge request gitlab-org/gitlab!77069

Fix N+1 problem for system notes metadata association

See merge request gitlab-org/gitlab!76951

Fix foreign key and index names on `ci_sources_pipelines` for old schemas

See merge request gitlab-org/gitlab!76171

Remove `force_company_trial` experiment

See merge request gitlab-org/gitlab!76982

Decomposed db:rollback pipeline

See merge request gitlab-org/gitlab!75954

Fix typo in variable name initialization

See merge request gitlab-org/gitlab!77066

Fixed table headers in project level variables docs

See merge request gitlab-org/gitlab!77067

Add test for chat integration deployment events

See merge request gitlab-org/gitlab!76785

Update GitLab version support link

See merge request gitlab-org/gitlab!77063

Update DS docs for SCA SEO and clarity

See merge request gitlab-org/gitlab!76911

Updated language for Kubernetes executor

See merge request gitlab-org/gitlab!77064

The `force_company_trial` experiment has been marked as a loser and this
MR is responsible for removing it.

* The `combined_registration` experiment will continue to use
  "force_company_trial" in it's context key as it is still running and
  there are conversions that we are still possible

part of:
https://gitlab.com/gitlab-org/gitlab/-/issues/345621

Changelog: removed

Hide feed, incoming email, and static access tokens by default

See merge request gitlab-org/gitlab!77037

Merge branch '348480-admins-should-be-able-to-set-the-new-user-sign-up-cap-at-a-value-higher-than-the-licensed' into 'master'

Resolve "Admins should be able to set the new user sign up cap at a value higher than the licensed user count"

See merge request gitlab-org/gitlab!76829

Merge branch 'jejacks0n/experiment/new_project_sast_enabled_add_unchecked_free_variant' into 'master'

Adds new unchecked free indicator variant

See merge request gitlab-org/gitlab!76899

Update secure_coding_guidelines.md

See merge request gitlab-org/gitlab!76992

Handle nil services error in external pipeline validation

See merge request gitlab-org/gitlab!76902

Fix typo in case "The" not "THe"

See merge request gitlab-org/gitlab!77038

Docs: Remove config example from k8s install & link to config page

See merge request gitlab-org/gitlab!75444

Remove redundant scope `with_files_stored_locally`

See merge request gitlab-org/gitlab!76557

When the `ci_sources_pipelines` table was first introduced in GitLab 9.3
EE, the foreign key names generate for the table appeared to have been
calculated via a hash using the table name
`ci_pipeline_source_pipelines`. This led to a merge conflict and
confusion during a CE to EE merge in GitLab 10.0, which regenerated the
schema with the correct foreign key names.

Hence anyone who installed GitLab prior to 10.0 may have been seeded the
database with stale, incorrect foreign key names.

During the Great BigInt Conversion of 2021, the migrations assumed that:

1. The foreign key `fk_be5624bf37` existed for `ci_sources_pipelines`.
2. The index `index_ci_sources_pipelines_on_source_job_id` existed.

However, older installations may have had the foreign key under the
original `fk_3f0c88d7dc` and
`index_ci_pipeline_source_pipelines_on_source_job_id`, respectively.

To eliminate future confusion and migration failures, we now rename the
foreign key constraints and index to what they should be today.

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

Changelog: fixed

Add guidance for granular version notes

See merge request gitlab-org/gitlab!76936

Service Ping in yaml + developer docs

See merge request gitlab-org/gitlab!76872