Loading
Enable Vue 3 migration rollout for Audit Events pages
What does this MR do and why?
Enable Vue 3 migration rollout for the Audit Events Vue app at ee/app/assets/javascripts/audit_events/.
This adds vue3_migration.yml files to the three Audit Events page entrypoints and introduces the vue3_migrate_audit_events feature flag. When the flag is enabled, Rails serves the Vue 3 (@vue/compat) chunk for all Audit Events pages; otherwise the Vue 2 chunk is served.
Pages covered:
ee/app/assets/javascripts/pages/admin/audit_logs/(Admin Audit Log)ee/app/assets/javascripts/pages/groups/audit_events/(Group Audit Events)ee/app/assets/javascripts/pages/projects/audit_events/(Project Audit Events)
All three pages share the same initAuditEvents entrypoint and the same AuditEventsApp root component, so a single feature flag covers all of them.
References
- Work item: #607943 (closed)
- Parent issue: #607904 (closed)
- Reference MR: !247789 (merged)
- Vue 3 migration guide: https://docs.gitlab.com/development/fe_guide/vue3_migration/
Screenshots or screen recordings
No UI changes — this is a build/runtime configuration change only.
| Before | After |
|---|---|
| N/A | N/A |
How to set up and validate locally
- Enable the feature flag:
Feature.enable(:vue3_migrate_audit_events) - Restart Vite:
gdk restart vite - Navigate to any Audit Events page (admin, group, or project)
- Open the browser console and confirm the message:
[gitlab] [V] Using Vue.js 3 (with @vue/compat) for AuditEventsView - Verify the Audit Events app renders and functions correctly
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.