This migration was finished at `2024-05-27 16:08:03 UTC`, you can confirm
the status using our
[batched background migration chatops commands](https://docs.gitlab.com/ee/development/database/batched_background_migrations.html#monitor-the-progress-and-status-of-a-batched-background-migration).
  To confirm it is finished you can run:

  ```
/chatops run batched_background_migrations status 1000547
```

The last time this background migration was triggered was in [db/post_migrate/20240516160731_queue_backfill_default_branch_protection_settings.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/post_migrate/20240516160731_queue_backfill_default_branch_protection_settings.rb)

  You can read more about the process for finalizing batched background migrations in
https://docs.gitlab.com/ee/development/database/batched_background_migrations.html .

  As part of our process we want to ensure all batched background migrations have had at least one
[required stop](https://docs.gitlab.com/ee/development/database/required_stops.html)
to process the migration. Therefore we can finalize any batched background migration that was added before the
last required stop.

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::OverdueFinalizeBackgroundMigration keep.

To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
label ~"GitLab Housekeeper" and consider pinging the author of this keep.

Changelog: other

Changelog: added

This will store cached rolled up weight values for work items

Changelog: other

This migration was finished at `2024-04-30 18:59:02 UTC`, you can confirm
the status using our
[batched background migration chatops commands](https://docs.gitlab.com/ee/development/database/batched_background_migrations.html#monitor-the-progress-and-status-of-a-batched-background-migration).
  To confirm it is finished you can run:

  ```
/chatops run batched_background_migrations status 1000506
```

The last time this background migration was triggered was in [db/post_migrate/20240419035620_queue_backfill_wiki_repository_states_project_id.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/post_migrate/20240419035620_queue_backfill_wiki_repository_states_project_id.rb)

  You can read more about the process for finalizing batched background migrations in
https://docs.gitlab.com/ee/development/database/batched_background_migrations.html .

  As part of our process we want to ensure all batched background migrations have had at least one
[required stop](https://docs.gitlab.com/ee/development/database/required_stops.html)
to process the migration. Therefore we can finalize any batched background migration that was added before the
last required stop.

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::OverdueFinalizeBackgroundMigration keep.

To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
label ~"GitLab Housekeeper" and consider pinging the author of this keep.

Changelog: other

This MR updates the
LicenseViolationChecker
to work with custom licenses

Changelog: changed
EE: true

As we want to enable this cop after fixing all the offenses.

Currently calling `Group#self_and_descendants` only includes
namespaces of the same type. As a result, ProjectNamespace
is always excluded. This change allows the caller to specify that
the results should include project namespaces.

Changes the `table_name` property on the `Ci::Pipeline`
model to use the routing table instead of the partition.
This change is under a feature flag disabled by default.

This migration was finished at `2024-02-14 00:00:02 UTC`, you can confirm
the status using our
[batched background migration chatops commands](https://docs.gitlab.com/ee/development/database/batched_background_migrations.html#monitor-the-progress-and-status-of-a-batched-background-migration).
  To confirm it is finished you can run:

  ```
/chatops run batched_background_migrations status 1000482
```

The last time this background migration was triggered was in [db/post_migrate/20240113071052_queue_populate_topics_slug_column.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/post_migrate/20240113071052_queue_populate_topics_slug_column.rb)

  You can read more about the process for finalizing batched background migrations in
https://docs.gitlab.com/ee/development/database/batched_background_migrations.html .

  As part of our process we want to ensure all batched background migrations have had at least one
[required stop](https://docs.gitlab.com/ee/development/database/required_stops.html)
to process the migration. Therefore we can finalize any batched background migration that was added before the
last required stop.

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::OverdueFinalizeBackgroundMigration keep.

To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
label ~"GitLab Housekeeper" and consider pinging the author of this keep.

Changelog: other

Changelog: other

# Conflicts:
#	db/structure.sql
#	lib/gitlab/database/partitioning_migration_helpers/table_management_helpers.rb

This migration will prepare an index
and allow more performant searches

Changelog: performance

Migration finished running in .com
so we can finalize it. Migration was scheduled
in 17.5 so it's safe to finalize in 17.6.

Changelo: other

This migration caused the BBM to begin erroring on .com because
application code is updated _before_ post-deployment migrations run. For
.com the issue was addressed by pausing the migration until the
post-deployment migrations were able to run an delete it. This change
converts the migration to a schema migration so that the same issue does
not happen during self-managed upgrades.

Changelog: fixed

We want to add a NOT NULL constraint to namespace.organization_id
column. In order to do so, we need to set a valid organization_id
in this column. This migration will take care of that

Changelog: changed

## What does this MR do and why?

Add and backfill namespace_id for analytics_cycle_analytics_value_stream_settings.

This table has a
[desired sharding key](https://docs.gitlab.com/ee/development/database/multiple_databases.html#define-a-desired_sharding_key-to-automatically-backfill-a-sharding_key)
configured ([view configuration](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/docs/analytics_cycle_analytics_value_stream_settings.yml)).

This merge request is the first step towards transforming the desired sharding key into a
[sharding key](https://docs.gitlab.com/ee/development/database/multiple_databases.html#defining-a-sharding-key-for-all-cell-local-tables).

This involves three changes:

- Adding a new column that will serve as the sharding key (along with the relevant index and foreign key).
- Populating the sharding key when new records are created by adding a database function and trigger.
- Scheduling a [batched background migration](https://docs.gitlab.com/ee/development/database/batched_background_migrations.html)
  to set the sharding key for existing records.

Once the background migration has completed, a second merge request will be created to finalize the background
migration and validate the not null constraint.

## How to verify

We have assigned a random backend engineer from ~"group::optimize" to review these changes. Please review this merge
request from a ~backend perspective. The main thing we are looking to verify is that the added column and association
match the values specified by the [desired sharding key](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/docs/analytics_cycle_analytics_value_stream_settings.yml)
configuration and that backfilling the column from this other table makes sense in the context of this feature.

When you are finished, please:

1. Trigger the [database testing pipeline](https://docs.gitlab.com/ee/development/database/database_migration_pipeline.html)
   as instructed by Danger.
1. Request a review from the ~backend maintainer and ~database reviewer suggested by Danger.

If you have any questions or concerns, reach out to `@tigerwnz` or @shubhamkrai.

This merge request was generated by a once off keep implemented in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/143774

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::BackfillDesiredShardingKeySmallTable keep.

To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
label ~"GitLab Housekeeper" and consider pinging the author of this keep.

Changelog: other

This migration was finished at `2024-04-11 09:04:05 UTC`, you can confirm
the status using our
[batched background migration chatops commands](https://docs.gitlab.com/ee/development/database/batched_background_migrations.html#monitor-the-progress-and-status-of-a-batched-background-migration).
  To confirm it is finished you can run:

  ```
/chatops run batched_background_migrations status 1000493
```

The last time this background migration was triggered was in [db/post_migrate/20240306120522_queue_update_sbom_occurrences_component_name_based_on_pep503.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/post_migrate/20240306120522_queue_update_sbom_occurrences_component_name_based_on_pep503.rb)

  You can read more about the process for finalizing batched background migrations in
https://docs.gitlab.com/ee/development/database/batched_background_migrations.html .

  As part of our process we want to ensure all batched background migrations have had at least one
[required stop](https://docs.gitlab.com/ee/development/database/required_stops.html)
to process the migration. Therefore we can finalize any batched background migration that was added before the
last required stop.

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::OverdueFinalizeBackgroundMigration keep.

To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
label ~"GitLab Housekeeper" and consider pinging the author of this keep.

Changelog: other

This commit adds a new not nul constraint at the database level
to prevent creating records without a project.

Changelog: other

- Add project_id/group_id/inherit_from_id columns to match existing
integrations table for easier transition of data
- Add IS NULL constraints to project_id/group_id/inherit_from_id since
these values will always be null for instance integrations
- Add instance=true constraint

Changelog: other

Changelog: added

Changelog: added

# Conflicts:
#	spec/lib/gitlab/database/sharding_key_spec.rb

Currently when a group or project access token is expiring, we notify
direct members of the project or group. This change adds a setting which
will default to notifying both direct and inherited members about the
expiring token, which can be disabled at the group level.

Changelog: added

We're transitioning from the boolean `namespace_details.pending_delete`
column to the new `deleted_at` timestamp column. This change improves
clarity, as `pending_delete` incorrectly suggests future scheduling
rather than an ongoing process.

The `deleted_at` column will now indicate when the background deletion
process for a group has started. This will also enable us to see when
the group was deleted to help in debugging if the group deletion fails.

Changelog: other

Add a user preference setting for text editor type:
rich text editor or plain text editor. Additionally, also
introduce a feature flag to set rich text editor as default
editor if the feature flag is enabled.

Changelog: added

pm_epss to pm_cve_enrichment and rename score column to epss_score

Changelog: changed

Changelog: other

Changelog: added

This migration was finished at `2023-10-02 14:43:05 UTC`, you can confirm
the status using our
[batched background migration chatops commands](https://docs.gitlab.com/ee/development/database/batched_background_migrations.html#monitor-the-progress-and-status-of-a-batched-background-migration).
  To confirm it is finished you can run:

  ```
/chatops run batched_background_migrations status 1000459
```

The last time this background migration was triggered was in [db/post_migrate/20230721095222_delete_orphans_approval_project_rules2.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/post_migrate/20230721095222_delete_orphans_approval_project_rules2.rb)

  You can read more about the process for finalizing batched background migrations in
https://docs.gitlab.com/ee/development/database/batched_background_migrations.html .

  As part of our process we want to ensure all batched background migrations have had at least one
[required stop](https://docs.gitlab.com/ee/development/database/required_stops.html)
to process the migration. Therefore we can finalize any batched background migration that was added before the
last required stop.

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::OverdueFinalizeBackgroundMigration keep.

To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
label ~"GitLab Housekeeper" and consider pinging the author of this keep.

Changelog: other

This migration was finished at `2024-10-10 02:02:03 UTC`, you can confirm
the status using our
[batched background migration chatops commands](https://docs.gitlab.com/ee/development/database/batched_background_migrations.html#monitor-the-progress-and-status-of-a-batched-background-migration).
  To confirm it is finished you can run:

  ```
/chatops run batched_background_migrations status 1000723
```

The last time this background migration was triggered was in [db/post_migrate/20240930135301_queue_backfill_dast_scanner_profiles_builds_project_id.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/post_migrate/20240930135301_queue_backfill_dast_scanner_profiles_builds_project_id.rb)

  You can read more about the process for finalizing batched background migrations in
https://docs.gitlab.com/ee/development/database/batched_background_migrations.html .

  As part of our process we want to ensure all batched background migrations have had at least one
[required stop](https://docs.gitlab.com/ee/development/database/required_stops.html)
to process the migration. Therefore we can finalize any batched background migration that was added before the
last required stop.

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::OverdueFinalizeBackgroundMigration keep.

To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
label ~"GitLab Housekeeper" and consider pinging the author of this keep.

Changelog: other

This migration was finished at `2024-10-15 09:30:03 UTC`, you can confirm
the status using our
[batched background migration chatops commands](https://docs.gitlab.com/ee/development/database/batched_background_migrations.html#monitor-the-progress-and-status-of-a-batched-background-migration).
  To confirm it is finished you can run:

  ```
/chatops run batched_background_migrations status 1000727
```

The last time this background migration was triggered was in [db/post_migrate/20240930143922_queue_backfill_dast_profiles_pipelines_project_id.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/post_migrate/20240930143922_queue_backfill_dast_profiles_pipelines_project_id.rb)

  You can read more about the process for finalizing batched background migrations in
https://docs.gitlab.com/ee/development/database/batched_background_migrations.html .

  As part of our process we want to ensure all batched background migrations have had at least one
[required stop](https://docs.gitlab.com/ee/development/database/required_stops.html)
to process the migration. Therefore we can finalize any batched background migration that was added before the
last required stop.

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::OverdueFinalizeBackgroundMigration keep.

To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
label ~"GitLab Housekeeper" and consider pinging the author of this keep.

Changelog: other

This migration was finished at `2024-09-19 01:01:02 UTC`, you can confirm
the status using our
[batched background migration chatops commands](https://docs.gitlab.com/ee/development/database/batched_background_migrations.html#monitor-the-progress-and-status-of-a-batched-background-migration).
  To confirm it is finished you can run:

  ```
/chatops run batched_background_migrations status 1000669
```

The last time this background migration was triggered was in [db/post_migrate/20240915140444_queue_backfill_alert_management_alert_metric_images_project_id.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/post_migrate/20240915140444_queue_backfill_alert_management_alert_metric_images_project_id.rb)

  You can read more about the process for finalizing batched background migrations in
https://docs.gitlab.com/ee/development/database/batched_background_migrations.html .

  As part of our process we want to ensure all batched background migrations have had at least one
[required stop](https://docs.gitlab.com/ee/development/database/required_stops.html)
to process the migration. Therefore we can finalize any batched background migration that was added before the
last required stop.

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::OverdueFinalizeBackgroundMigration keep.

To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
label ~"GitLab Housekeeper" and consider pinging the author of this keep.

Changelog: other

We added this batched background migration in a previous MR. [^1]

The [Batched Background Migration docs][0] say to finalize a migration
when two conditions are met:

1. The batched background migration is completed on GitLab.com
2. The batched background migration was added in or before the last
   required stop

* I verified with chatops that the migration is complete.[^2]
* The background migration is available in [`v17.5.0-ee`][1], which is
  a [required stop][2]

[^1]: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/166110
[^2]:https://gitlab.com/gitlab-org/gitlab/-/issues/486530#note_2128952648

[0]:https://docs.gitlab.com/ee/development/database/batched_background_migrations.html#finalize-a-batched-background-migration
[1]:https://gitlab.com/gitlab-org/security/gitlab/-/tree/v17.5.0-ee
[2]:https://gitlab.com/gitlab-org/gitlab/-/blob/1842050872cc3a4062de067f9dbe6b86f1d9cd36/config/upgrade_path.yml#L77-79

---

related to: https://gitlab.com/gitlab-org/gitlab/-/issues/486530
resolves: https://gitlab.com/gitlab-org/gitlab/-/issues/496437
epic: https://gitlab.com/groups/gitlab-org/-/epics/15036
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/170521
Changelog: changed