Re-create migrations previously skipped for GitLab.com
Because of &7249 (comment 819662046) we skip some migrations to remove FKS on GitLab.com
Proposal
After the manual change management to remove the FKs manually on GitLab.com, we should create new migrations with different VERSIONs to ensure these FKs are removed for sure :
-
db/post_migrate/20220121214752_remove_projects_ci_stages_project_id_fk.rb: return if Gitlab.com? # unsafe migration, skip on GitLab.com due to &7249 (comment 819625526) -
db/post_migrate/20220124153233_remove_projects_ci_job_artifacts_project_id_fk.rb: return if Gitlab.com? # unsafe migration, skip on GitLab.com due to &7249 (comment 819625526) -
db/post_migrate/20220124180704_remove_projects_ci_builds_metadata_project_id_fk.rb: return if Gitlab.com? # unsafe migration, skip on GitLab.com due to &7249 (comment 819625526) -
db/post_migrate/20220126210021_remove_projects_ci_builds_project_id_fk.rb: return if Gitlab.com? # unsafe migration, skip on GitLab.com due to &7249 (comment 819625526)
See also
Edited by Kamil Trzciński