Although this feature is flagged, it has a DB migration so
a changelog should be included.

Abstract with release presenter

See merge request gitlab-org/gitlab!18724

This commit abstracts FE specific code with release presenter

Add project option for deleting source branch

Closes #18283

See merge request gitlab-org/gitlab!18408

Feature branches should be deleted after being merged into a stable
branch like master. This is not universally true, and accidentally
deleting a branch cause frustration and confusion for users.

The change:
- adds a Project Setting to control if 'Delete source branch' option is
enabled or disabled for new merge requests
- the Project Setting is on for new and existing projects

The previous default behaviour can be restored by toggling the new
setting.

Historically, the behaviour was changed to delete the source branch as
part of the merge widget refactor and then reverted 3 months later.

- Widget refactor 8db76243
- Behaviour reverted fd72b4ed

Migrate only AttachmentUploader note uploads

See merge request gitlab-org/gitlab!18873

Fix rake task to rollback Geo migrations

See merge request gitlab-org/gitlab!18975

ActiveRecord Migrator API has changed in 5.2,
and now MigrationContext class must be used.

Add custom modsecurity template to ingress-controller

Closes #8558

See merge request gitlab-org/gitlab!18485

Disable default `SecRuleEngine` configuration, allowing override via
`Ingress` resource instead.

Part of the work to implement https://gitlab.com/gitlab-org/gitlab/issues/8558

Show the sync information for design repositories

Closes #13055

See merge request gitlab-org/gitlab!18379

Adds Geo Node API and sync status in Admin panel

Geo: make console messages consistent

See merge request gitlab-org/gitlab!16584

Group Based Cycle Analytics Backend

Closes #12196

See merge request gitlab-org/gitlab!18452

This MR extends the Cycle Analytics query classes to handle Group based
stages. The change happens within `ee`: group based CA is a premium
feature.

This change also sets up the `data_collector_spec.rb` file, where
various `start_event` and `end_event` pairs will be tested.

Related Issue: https://gitlab.com/gitlab-org/gitlab/issues/12196

Improve our Sidekiq testing best practices

See merge request gitlab-org/gitlab!19008

Fix broken master due to Sidekiq usage

See merge request gitlab-org/gitlab!19022

We switched to Sidekiq.fake when running tests but this test
needs the worker to run inline

Adding status mirroring to the CI/CD reference

See merge request gitlab-org/gitlab!19007

Tracking experimental signup flow

See merge request gitlab-org/gitlab!17521

Resolve "Fully revert privacy update banner as redundant to ToS"

Closes #34570

See merge request gitlab-org/gitlab!18900

- Since we already have a terms of service that handles
  the privacy policy updates, this code can be removed.

Fix failing spec ScheduleFixGitlabComPagesAccessLevel

Closes #34758

See merge request gitlab-org/gitlab!19002

We recently switched from inline to fake mode for sidekiq, so the
MR which introduced this change also changed existing sidekiq specs
to use inline explicitly, but this failing spec was merged meantime.

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

Record latencies for sidekiq failures

Closes gitlab-com/gl-infra/scalability#46

See merge request gitlab-org/gitlab!18909

Document finding objects by id in GraphQL

See merge request gitlab-org/gitlab!18648

We prefer not exposing a database ID directly.

Sort vulnerabilities for pipeline dashboard

See merge request gitlab-org/gitlab!18863

Consider enum values rather than string
Added further test

Inherit children epics start and due dates

See merge request gitlab-org/gitlab!14366

Epic would now inherit start_date or end_date from its
related issues milestone dates or from child epic
depending on which one gives the wider time spread.

Uses a single update statement to update start_date, due_date,
start_date_sourcing_milestone_id, start_date_sourcing_epic_id,
due_date_sourcing_milestone_id, due_date_sourcing_epic_id

Epic inherited dates update for multiple epics moved to
an async worker

Update epic dates in batches

Add foreign key constraints and indexes on
start_date_sourcing_epic_id and due_date_sourcing_epic_id

https://gitlab.com/gitlab-org/gitlab-ee/issues/7332

Documentation: Update webhooks.md: clarify the risk / attack scenario concerning web hooks

See merge request gitlab-org/gitlab!18203

Update webhooks.md: damn browser or web IDE added 2 new whitespaces when fixing wrapping, removed whitespace again