## Overview Vue 2 has been end-of-life since December 31, 2023 — over 2.5 years without security patches. For our FedRAMP customers, running an unsupported framework is an active compliance risk that grows every month. The infrastructure to make Vue 3 migration as painless as possible has been built; now the Sessions team needs to pick it up and migrate their pages. ## Why migrate now - **Security & compliance**: Vue 2 is EOL with no security patches. This is an active FedRAMP compliance risk. - **Better AI-assisted development**: Vue 3 is the default in all current documentation, tutorials, and community examples. AI coding tools (Duo and others) are trained predominantly on Vue 3 patterns — suggestions for Vue 2 code are frequently inaccurate or require manual correction. Migrating directly improves the quality of AI-generated code. - **Modern libraries**: Vue 3 unlocks libraries teams have been asking for (e.g. `vue-flow` for workflow visualization), along with actively maintained versions of existing dependencies. - **Better TypeScript support**: Vue 3 was built with TypeScript from the ground up — types are accurate and inference works properly, opening doors for broader TS adoption in our codebase. ## What needs to be done Migrate all Sessions pages to Vue 3. The new tooling makes this straightforward: 1. Add a feature flag 2. Add a YAML file per entrypoint (`vue3_migration.yml`) 3. Smoke test key workflows ## Resources - **Migration steps**: https://docs.gitlab.com/development/fe_guide/vue3_migration/#option-1-recommended-migrate-your-page-entrypoint-using-a-feature-flag-and-vue3_migrationyml - **Example migration MR**: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/247789 ## Review & support - Assign migration MRs to `@mrincon` , `@xanf` or `@ntepluhina` for review. - For questions or issues, reach out in **#vue3_migration** on Slack.