[merge-train skip]

[ci skip]

Prepare 17.9.6 release for gitlab-jh

See merge request gitlab-cn/gitlab!3077

[merge-train skip]

[ci skip]

Prepare 17.9.5 release for gitlab-jh

See merge request gitlab-cn/gitlab!3073

[merge-train skip]

[ci skip]

Prepare 17.9.4 release for gitlab-jh

See merge request gitlab-cn/gitlab!3070

[merge-train skip]

[ci skip]

[ci skip]

[merge-train skip]

[ci skip]

[ci skip]

Ensure runner taggings are copied from taggings

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/186278



Merged-by: Mayra Cabrera <mcabrera@gitlab.com>
Approved-by: Pedro Pombeiro <noreply@pedro.pombei.ro>
Co-authored-by: Max Woolf <mwoolf@gitlab.com>
Co-authored-by: Marius Bobin <mbobin@gitlab.com>

Changelog: fixed

[merge-train skip]

[ci skip]

Prepare 17.9.3 release for gitlab-jh

See merge request gitlab-cn/gitlab!3051

Merge branch 'pedropombeiro/520092/backports/17.9/no-op-ci_runner_machines_687967fa8a-backfill' into '17-9-stable-ee' 

No-op ci_runner_machines_687967fa8a batched migrations - 17.9 backport

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/185303



Merged-by: Jenny Kim <yjeankim@gitlab.com>
Approved-by: Marius Bobin <mbobin@gitlab.com>
Co-authored-by: Pedro Pombeiro <noreply@pedro.pombei.ro>

The backfill on this table is causing issues due to a problem in the
timing of the post-deployment migrations:

1. 20241107064635_queue_backfill_ci_runner_machines_partitioned_table
2. 20241211072300_retry_add_fk_from_p_ci_runner_managers_to_p_ci_runners
3. 20241219100359_requeue_backfill_ci_runners_partitioned_table

Migration 2 installs a FK check before the target table
(ci_runners_e59bb2812d) is backfilled in migration 3,
so we have https://gitlab.com/gitlab-org/gitlab/-/issues/520092.
We can afford to not backfill ci_runner_machines_687967fa8a,
since it'll be populated with runner data automatically as they
request jobs from the GitLab instance.

Changelog: other

[merge-train skip]

[ci skip]

[ci skip]