NOP migration that finalizes migration to add PAT expiration
What does this MR do and why?
This backports !158161 (closed) to 17-1-stable-ee
.
In GitLab 17.1 !154302 (merged) dropped CleanupPersonalAccessTokensWithNilExpiresAt
and a number of other background migration classes. As a result, if this finalize step
actually ran, the batched background migration would hit an error.
NOP this migration since it won't do anything now.
Related to https://gitlab.com/gitlab-org/gitlab/-/issues/462157
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:package-and-test-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 Stan Hu