[Feature flag] Rollout of vue3_migrate_artifacts

Summary

Roll out the feature currently behind the vue3_migrate_artifacts feature flag.

• DRI: @mrincon
• Team Slack channel: TBD

Note

Process and guidance live in the docs — this issue is just the commands and a place to track the rollout. "Rolling out" means incrementally enabling the flag on GitLab.com to validate stability — it is not the same as releasing the feature, which happens when the flag is removed. Feature flag controls · Feature flag lifecycle

What could go wrong?

Blast radius is the three artifacts pages. No data is written by the flag, so there is no data-loss risk.

Watch for:

• The artifacts table on projects/artifacts fails to render or its Apollo queries break. This is the only page of the three that mounts its own Vue app.
• projects/artifacts/file and projects/artifacts/browse mount no Vue app directly, so neither page carries a data-gitlab-vue3-app marker. A silent fallback is invisible. Check which chunk loads in the network tab.
• The blob viewers load lazily, so a regression shows only when a user opens an artifact of that type. Check a notebook, a PDF and a CSV artifact by hand.

Rollout

Run all production /chatops in #production and cross-post the results to TBD. Background: incremental rollout process, feature actors.

Non-production

/chatops gitlab run feature set vue3_migrate_artifacts 50 --actors --dev --pre --staging --staging-ref
/chatops gitlab run feature set vue3_migrate_artifacts true --dev --pre --staging --staging-ref

Production — percentage rollout (wait ≥15 min between steps, watch dashboards):

/chatops gitlab run feature set vue3_migrate_artifacts <percentage> --actors

Or target specific actors instead:

/chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss vue3_migrate_artifacts true
/chatops gitlab run feature set --group=gitlab-org,gitlab-com vue3_migrate_artifacts true
/chatops gitlab run feature set --user=mrincon vue3_migrate_artifacts true

Before global rollout

Confirm the relevant gotchas before going to 100% — see enabling a feature for GitLab.com:

• Docs + version history updated
• Breaking changes announced, if any
• Change management issue opened, if required
• External API consumers handled with a fail-open mechanism, if applicable

Cleanup

Remove the flag once deemed stable — see cleaning up. Track it here, or open a follow-up Feature Flag Cleanup issue. Remove the flag and its YAML definition from the codebase, then:

/chatops gitlab run release check <merge-request-url> <milestone>
/chatops gitlab run feature delete vue3_migrate_artifacts --dev --pre --staging --staging-ref --production

Rollback

/chatops gitlab run feature set vue3_migrate_artifacts false                                         # production
/chatops gitlab run feature set vue3_migrate_artifacts false --dev --pre --staging --staging-ref     # non-production
/chatops gitlab run feature delete vue3_migrate_artifacts --dev --pre --staging --staging-ref --production  # remove entirely