That was six years ago, predating extension registration – I would assume that nowadays extensions are supposed to declare their compatible MediaWiki versions in extension.json https://www.mediawiki.org/wiki/Manual:Extension_registration#Requirements_(dependencies) (details https://www.mediawiki.org/wiki/Manual:Extension.json/Schema#requires).
Cheers, Lucas
Am Fr., 15. Nov. 2019 um 16:38 Uhr schrieb Stephan Gambke via Wikitech-l < wikitech-l@lists.wikimedia.org>:
See https://github.com/wikimedia/mediawiki/commit/3307d4957925df319df2b84cfc3e6f...
"This change allows extensions to specify they depend on a specific version or version range of MediaWiki. This is done by adding the package mediawiki/mediawiki in their composer.json require section."
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, November 15, 2019 4:15 PM, David Barratt < dbarratt@wikimedia.org> wrote:
as far as I know, extensions shouldn't be declaring a dependency on
MediaWiki in composer.json and if one is, it should probably be fixed.
On Fri, Nov 15, 2019 at 9:50 AM Stephan Gambke via Wikitech-l <
wikitech-l@lists.wikimedia.org> wrote:
When running `composer update` MediaWiki injects a mediawiki/mediawiki
package, so extensions can declare a dependency on a particular MW version range.
However, when doing a `composer update --dry-run` this package gets not
injected causing the dry run to fail.
Does anybody know a solution/workaround?
Stephan
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l