## Why * Vue 2 has been EOL since December 2023 — an active compliance risk for FedRAMP customers. * AI coding tools (Duo and others) produce better suggestions against Vue 3 code. * Unlocks Vue 3-only libraries and proper TypeScript support. ## References - [Vue 3 migration dashboard ](https://vue3-migration-dashboard-0afc95.gitlab.io/) ## What we migrate The 13 page entrypoints owned by Vulnerability Management and Agentic Security Flows: | Area | Pages | | --- | --- | | Dependency list | project, group | | Vulnerability report | project, group, instance | | Pipeline Security Tab | project | | Vulnerability details | details page, new vulnerability page | | Security dashboard | project, group, organization, instance, instance settings | Not in scope: the security configuration page and the security inventory page. Those live in code we do not own in CODEOWNERS, so another group picks them up. ## How Per the [migration guide](https://docs.gitlab.com/development/fe_guide/vue3_migration/#option-1-recommended-migrate-your-page-entrypoint-using-a-feature-flag-and-vue3_migrationyml), each page needs: 1. A feature flag. 2. A `vue3_migration.yml` file next to its `index.js`. 3. Manual testing with the flag on. No app code changes are needed to opt in. We only change code to fix what we find. [Example MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/247789). One helpful head start: the pipeline security tab already runs on Vue 3 under the `vue3_migrate_pipelines` rollout. That covers most of the shared vulnerability report, the filtered search tokens, and the router and Apollo shims. A large part of our code is already proven in production. ## Steps Ordered from lowest risk to highest (but does not need to be done in this order, except for step 0) - [x] Step 0: [small fixes before we start](https://gitlab.com/gitlab-org/gitlab/-/issues/607914) - [ ] Step 1: [dependency list](https://gitlab.com/gitlab-org/gitlab/-/issues/607915) - [ ] Step 2: [pipeline security tab](https://gitlab.com/gitlab-org/gitlab/-/work_items/609371) - [ ] Step 3: [vulnerability report](https://gitlab.com/gitlab-org/gitlab/-/issues/607916) - [ ] Step 4: [vulnerability details](https://gitlab.com/gitlab-org/gitlab/-/issues/607918) - [ ] Step 5: [security dashboard](https://gitlab.com/gitlab-org/gitlab/-/issues/607919) ## Help Add the `pipeline:run-rspec-vue3` label to every migration MR. Assign MRs to `@mrincon`, `@xanf` or `@ntepluhina` for review. Ask questions in `#vue3_migration`.