Roll out the pipeline Security tab under vue3_migrate_pipelines

Miguel Rinconrequested to merge
vue3-merge-pipeline-security-tab-flag into master

What does this MR do and why?

The pipeline Security tab entrypoint (ee/app/assets/javascripts/pages/projects/pipelines/security/) rolls out to Vue 3 behind its own flag, vue3_migrate_pipeline_security_tab. The tab renders the same pipelines/show page. It reaches no component that vue3_migrate_pipelines does not already cover (151 of 151 shared, see #629301).

Two flags over one code path double the rollout work without adding coverage. This MR:

  • Points the Security tab vue3_migration.yml at vue3_migrate_pipelines.
  • Removes the vue3_migrate_pipeline_security_tab flag definition.

Both flags are at the same stage on production today (enabled for the same feature group), so this changes nothing for current users.

The original migration issue #609371 (closed) and !250177 (merged) planned to reuse vue3_migrate_pipelines. The separate flag was added during review.

References

  • Related to #629301
  • Related to #617015 (closed) (rollout issue, can close once this merges and the flag is deleted with chatops)
  • Rollout continues in #594278

How to set up and validate locally

  1. Enable vue3_migrate_pipelines.
  2. Restart vite: gdk restart vite.
  3. Open a pipeline with security scan results and switch to the Security tab.
  4. Confirm the security dashboard renders (findings table, filters, severity badges, finding drawer).
  5. Confirm document.querySelectorAll('[data-gitlab-vue3-app]') reports the app on Vue 3.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist.

🤖 Generated with Claude Code

Merge request reports