Use dump from 17.3.5 since 17.3 is the previous required stop
What does this MR do and why?
Describe in detail what merge request is being backported and why
Use PG dump from 17.3.5 since 17.3 is the previous required stop before 17.4. This will help prevent failures in the db:migrate:multi-version-upgrade
like https://gitlab.com/gitlab-org/release/tasks/-/issues/13750. https://gitlab.com/gitlab-org/release/tasks/-/issues/13750#note_2169178386 has an explanation for what caused the jobs to fail.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch. The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes).-
This MR has a severity label assigned (if applicable). -
Set the milestone of the merge request to match the target backport branch version. -
This MR has been approved by a maintainer (only one approval is required). -
Ensure the e2e:test-on-omnibus-ee
job has either succeeded or been approved by a Software Engineer in Test.
Note to the merge request author and maintainer
If you have questions about the patch release process, please:
- Refer to the patch release runbook for engineers and maintainers for guidance.
- Ask questions on the
#releases
Slack channel (internal only).
Edited by Reuben Pereira