Update CI/CD catalog `versions` to use `latest_version`"
requested to merge 415497-frontend-update-ci-cd-catalog-versions-first-1-field-on-index-page-to-use-latest_version into master
What does this MR do and why?
For performance reasons, we are deprecating the versions
field on graphql type CiCatalogResources
. Instead, we should use latest_version
Screenshots or screen recordings
No visual changes
Before | After |
---|---|
How to set up and validate locally
- Make sure you have an ultimate license for your GDK
- Enable the feature flag:
ci_namespace_catalog_experimental
- Login as a user
- Create a few projects that you will be able to convert to Ci resources (ideally 20+).
- Once you have done so, get the ID of the first new project you wanted to convert. Then in Rails console, run:
projects = Project.where("id > ?", your_first_project_id)
projects.each do |project|
project.update!(description: 'description')
::Ci::Catalog::Resource.new(project_id: project.id).save
end
- Navigate to
/$namespace/$project/-/ci/catalog/resources
- Notice that you can see "Unreleased" tag
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.
Related to #415497 (closed)
Edited by Frédéric Caplette