It has been enabled by default since 14.3

Changelog: other

Add 'Explore topics' page

See merge request gitlab-org/gitlab!62443

Quarantine issue board label spec and remove reliable tag

See merge request gitlab-org/gitlab!73659

Remove new_customersdot_staging_url feature flag

See merge request gitlab-org/gitlab!73666

Explain why JIRA DVCS requires API write-access

See merge request gitlab-org/gitlab!73707

Add policy name to ScanExecutionPolicyCommit mutation

See merge request gitlab-org/gitlab!71994

Ignore customer sync for project namespaces

See merge request gitlab-org/gitlab!72986

Cleanup sticky_environments_in_job_retry feature flag

See merge request gitlab-org/gitlab!73606

git: Fix object pool spec checking for wrong reference

See merge request gitlab-org/gitlab!73620

Update UI link to new conflicts page

See merge request gitlab-org/gitlab!73565

Explain "Deleted User" Audit Events in docs

See merge request gitlab-org/gitlab!72223

Merge branch '342715-db-timeout-when-loading-environment-in-projects-blobcontroller-show-2' into 'master'

Optimize EnvironmentsByDeploymentFinder

See merge request gitlab-org/gitlab!72781

Fixing small typo in comment

See merge request gitlab-org/gitlab!73566

More fully document documentation pipelines and Docker images

See merge request gitlab-org/gitlab!73436

Remove not_null constraint and default for public_email

See merge request gitlab-org/gitlab!72514

The DVCS connector uses the application token over GitLab API calls to
perform some of its required webhook configuration.

For this to succeed, the wider api scope needs to be selected instead
of the limited read_api scope.

The integration cannot function successfully if the read-only scope
is provided instead.

Related issue: https://gitlab.com/gitlab-org/gitlab/-/issues/343942

Remove failing test from reliable suite

See merge request gitlab-org/gitlab!73701

danger: Don't override already-set scoped labels

See merge request gitlab-org/gitlab!73676

Add webhook rate limits to rate limits page

See merge request gitlab-org/gitlab!73689

Update user analytics page to make features more prominent

See merge request gitlab-org/gitlab!73619

Combine and refine pipeline artifacts deletion information

See merge request gitlab-org/gitlab!73520

Pared down and moved release keyword content

See merge request gitlab-org/gitlab!73108

Clarify that administrator is not a role

See merge request gitlab-org/gitlab!73667

Add container registry to object storage

See merge request gitlab-org/gitlab!71905

Add primary email to emails upon confirmation

See merge request gitlab-org/gitlab!70872

Fix merge request commits that are missing committer/author details

See merge request gitlab-org/gitlab!73307

Update user attributes for Group SAML enterprise users

See merge request gitlab-org/gitlab!72792

Consolidate the logic for SAST prompt experiment

See merge request gitlab-org/gitlab!73034

Filter Dast Profiles with Schedule

See merge request gitlab-org/gitlab!72301

Improve error tracking error handling

See merge request gitlab-org/gitlab!73557

In MR https://gitlab.com/gitlab-org/gitlab/-/merge_requests/63669 we
introduced a new data format for storing merge request diff commit
authors and committers. As part of this work we made changes to the
import/export code to support this new format, and added a set of
migrations to migrate existing data to this new format. At this time we
supported reading and writing of data in both the old and new format,
allowing us to gradually migrate data over to the new format.

In https://gitlab.com/gitlab-org/gitlab/-/merge_requests/72219 we
ensured all migrations are done, stopped using the old data format, and
removed the columns storing this data.

Unfortunately, this chain of events uncovered a bug in our import/export
logic. Consider the following timeline of events:

1. You export project "Cooking Recipes" from a GitLab instance running a
   version earlier than 14.1 (e.g. 14.0).
2. The instance you intend to import this project into is running 14.1
   or newer. Existing data has been fully migrated already.
3. You import the project into this new instance.

At this point, the imported data is using the old format, not the
format. This is because we forgot to take into account users importing
exports using GitLab 14.0 or older, instead only covering exports
generated using GitLab 14.1 or newer. Because the background migrations
finished, or the data imported would fall in a "bucket" (= a chunk or
rows to migrate) that had already been migrated, the data would never be
updated to the new format.

In this commit we resolve this problem in two steps. First, we change
the import/export logic to support importing data in both the old and
new format. Exports still use the new format. In addition, we include a
background migration that processes all projects created using a GitLab
import/export since the first mentioned merge request was introduced.
For each such project we scan over the merge request diff commits and
fix any that are missing the commit author or committer details.

For small self-hosted instances this process is unlikely to take more
than a few minutes. On GitLab.com however we expect this process to take
a few days, as we have to process around 200 000 projects imported since
July. This means we'll likely need additional manual intervention
similar to the manual work needed for
https://gitlab.com/gitlab-org/gitlab/-/issues/334394.

See https://gitlab.com/gitlab-org/gitlab/-/issues/344080 for additional
details.

Changelog: fixed

Redirected topic that was viewed infrequently

See merge request gitlab-org/gitlab!73684