The previous background migration left around 400.000 artifacts without
an expiry date. This schedules the background migration again to
backfill those entries as well.

The column `total_tuple_count` has only been introduced after the
migration helper had been used for the first time. That is, there is a
preceding migration using the helper. This migration and its schema
version does not know about the later column addition and hence the code
path fails.

We check if the attribute exists here, so we can safely work with it.

This is only needed in code paths that are already being used in
existing migrations.

See https://gitlab.com/gitlab-org/gitlab/-/issues/327447

The previous background migration missed 10 jobs, so this time we
will be tracking the jobs by passing in the track_jobs: true
parameter.

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

This commit optimizes the query for seraching
cherry picked merge requests through `notes` table.

This reverts merge request !57520

https://gitlab.com/gitlab-org/gitlab/-/issues/322637

Creates the cascading namespace concern, and defines the
delayed_project_removal attribute as the first cascading
attribute.

- Add habtm relationship between Dast::Profile and Ci::Pipeline
- Amend services to rely on Dast::Profile and create association
- Add EE Contextable override to retrieve Dast::Profile variables
- Extract shared example

Fixes auto correct rubocop offenses

Database optimizations to support epics filtering by
award emoji.

Refactor naming into more readable

Add new database column

Add specs and model method

Add specs for group saml session enforcer class

WIP on git access specs

Refactor git access specs

Add specs to git access

Add new setting to view and form

Add new setting to controller

Add changelog entry

Add translations file

Refactor git access class

Add method to find group

Fix container method

Add cr remarks

Simplify spec example

Change copy in saml sso form

Add documentation regarding checking sso session on git activity

Add cr remarks

Reorganize code to make sso check more effective

Add remarks to git check migration

Add remarks about enforcing sso on Git activity docs

Move check_additional_conditions method

Sends notification to users when their
SSH key has expired.
Cron job runs daily at 2 am UTC.

This is the last step of the partitioning operation.

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

This commit optimizes the database query for
last deployment by introducing a new database index.

This commit adds all the necessary database changes required to
replicate pipeline artifacts with geo.

- Add new temporary column id_convert_to_bigint to
  events table
- Add triggers to keep events.id_convert_to_bigint
  in sync with events.id
- Create batched background migration with job
  CopyColumnUsingBackgroundMigrationJob to backfill
  events.id_convert_to_bigint
- Add new tenmporary column event_id_convert_to_bigint to
  push_event_payloads table
- Add triggers to keep push_event_payloads.event_id_convert_to_bigint
  in sync with push_event_payloads.event_id
- Create batched background migration with job
  CopyColumnUsingBackgroundMigrationJob jobs to backfill
  push_event_payloads.event_id_convert_to_bigint

New table `vulnerability_finding_evidences`

This column will be used to distinguish cloud licenses from
legacy/offline licenses.

This foreign key constraint prevents creating inconsistent records.

of the projects deployments API endpoint.

MR: gitlab.com/gitlab-org/gitlab/-/merge_requests/57691
Issue: gitlab.com/gitlab-org/gitlab/-/issues/218410#note_535143110

Leveraging the work done for Package File Verification. Most of the
changes are to the database schemas, and to specs. Verification is
behind the feature flag "geo_snippet_repository_verification".

Add a new setting to the Jira integration to attempt an "automatic"
transition of Jira issues, by checking the available workflow
transitions on the issue and using the first one with a status
category of "Done".

Automatic transitions are enabled by setting the new DB column
`jira_issue_transition_automatic` to true, which takes precedence over
the existing `jira_issue_transition_id` column.

To make this behaviour opt-in, we also introduce an explicit checkbox
to enable issue transitions. The state of this checkbox is handled
entirely on the frontend, based on the values in
`jira_issue_transition_id` and `jira_issue_transition_automatic`.