Draft: Prepare Pages deployment to Multiple Versions
What does this MR do and why?
Prepare Pages deployment to Multiple Versions
With the work to introduce Gitlab Pages Multiple Versions, a project
now have to support multiple PagesDeployment at the same time.
For this reason, instead of using
ProjectPagesMetadatum#pages_deployment_id to identify valid
deployment the PagesDeployment#deleted_at field was [introduced].
Now, we're replacing the code that relied on
ProjectPagesMetadatum#pages_deployment_id, to use the new
PagesDeployment#deleted_at to identify a project active pages
deployments.
Related to:
Changelog: changed
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.