Page MenuHomePhabricator

Consider using library-upgrader to manage Vue-related dev dependencies
Open, LowestPublic1 Estimated Story Points

Description

Existing Vue projects in MediaWiki all pin different versions of Vue-related packages like Vue, vue-test-utils, Vue3-jest, etc. We should identify all commonly used packages for Vue projects and consider registering them with library-upgrader to offload maintenance on individual teams.

Inspired by this thread

Event Timeline

The particular need right now is T302129 / T302831 but yes, a general solution for keeping these up-to-date would be great. Using LibUp for this would be possible but challenging as every change needs manual local fixes in each repo, IME.

Using LibUp for this would be possible but challenging as every change needs manual local fixes in each repo, IME.

I agree that for the big Vue 2 -> Vue 3 migration, using LibUp would be challenging. But I would think that it would be much simpler to have LibUp manage minor version upgrades of those packages (e.g. upgrade from Vue 3.2.23 to 3.2.31 everywhere) once the big migration is done.

Change 818198 had a related patch set uploaded (by Catrope; author: Catrope):

[labs/libraryupgrader/config@master] releases: Add Codex at version 0.1.0-alpha.8

https://gerrit.wikimedia.org/r/818198

Change 818226 had a related patch set uploaded (by Catrope; author: Catrope):

[labs/libraryupgrader/config@master] releases: Add vue, @vue/compat and @vue/compiler-sfc

https://gerrit.wikimedia.org/r/818226

Change 818226 merged by jenkins-bot:

[labs/libraryupgrader/config@master] releases: Add vue, @vue/compat and @vue/compiler-sfc

https://gerrit.wikimedia.org/r/818226

Reopening because I'd also like us to manage @vue/test-utils and friends this way.

ldelench_wmf set the point value for this task to 1.Sep 19 2022, 3:40 PM