JSDuck has introduced various new annotations (such as @fires to complement @Event which we're already using). However 4.x and 5.x is a pretty significant upgrade so we should make sure we're compatible and there are no regressions before we upgrade.
Version: unspecified
Severity: enhancement
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Krinkle | T59039 Jenkins: Add jsduck test for OOjs and OOjs UI | |||
| Resolved | None | T57753 [OPS] Jenkins: Upgrade jsduck from v4.x to v5.x | |||
| Resolved | Krinkle | T57752 Migrate MediaWiki core jsduck settings to work with JSDuck 5 |
Related changes:
Related changes:
Related changes:
This was the last required change. Though the previous two changes in mediawiki-core did enough to make it jsduck v5 compatible, the jenkins job was still using the jsduck/config.json file directly instead of the maintenance script (which has where jsduck v4/v5 compat switch is).
We're now safe to upgrade.