The MyVariables extension adds new built-in variables (Home page).
Details
Sep 11 2024
Patch set above is for a different thing, but has a typo'd task in the commit message.
Change #1072155 had a related patch set uploaded (by Mhorsey; author: Mhorsey):
[mediawiki/extensions/CampaignEvents@master] Move card template to WikimediaCampaignEvents extension
Aug 20 2024
Aug 19 2024
Change #1063735 merged by jenkins-bot:
[mediawiki/extensions/MyVariables@REL1_42] Add support for fetching other pages' image using {{pageimage}}
Change #1063735 had a related patch set uploaded (by BlankEclair; author: BlankEclair):
[mediawiki/extensions/MyVariables@REL1_42] Add support for fetching other pages' image using {{pageimage}}
Change #1059354 merged by jenkins-bot:
[mediawiki/extensions/MyVariables@master] Add support for fetching other pages' image using {{pageimage}}
Aug 2 2024
Change #1059354 had a related patch set uploaded (by BlankEclair; author: BlankEclair):
[mediawiki/extensions/MyVariables@master] Add support for fetching other pages' image using {{pageimage}}
Jul 21 2023
Change 940444 merged by jenkins-bot:
[mediawiki/extensions/DisplayTitle@REL1_40] Add name and description properties to composer.json
Change 940445 merged by jenkins-bot:
[mediawiki/extensions/DisplayTitle@REL1_39] Add name and description properties to composer.json
Change 940445 had a related patch set uploaded (by Cicalese; author: Cicalese):
[mediawiki/extensions/DisplayTitle@REL1_39] Add name and description properties to composer.json
Change 940444 had a related patch set uploaded (by Cicalese; author: Cicalese):
[mediawiki/extensions/DisplayTitle@REL1_40] Add name and description properties to composer.json
Jul 17 2023
Change 938469 merged by jenkins-bot:
[mediawiki/extensions/DisplayTitle@master] Add name and description properties to composer.json
Change 938469 had a related patch set uploaded (by Cicalese; author: Cicalese):
[mediawiki/extensions/DisplayTitle@master] Add name and description properties to composer.json
Jul 12 2023
Jun 9 2023
@Reception123 - sorry for the long delay in responding. I tried this, and {{CURRENTUSER}} displayed fine for me, on both an unapproved page and a page with an approved revision. Thus, I'm guessing it was fixed, either due to that change in MyVariables, or maybe due to some change in Approved Revs, or maybe even a change in MediaWiki itself. In any case, I'm marking this as "Resolved"; though feel free to re-open this if you think it's still an issue.
Jun 8 2023
Change 928164 merged by jenkins-bot:
[mediawiki/extensions/ReplaceText@master] Add lines to composer.json to make it valid
Change 928164 had a related patch set uploaded (by Yaron Koren; author: Yaron Koren):
[mediawiki/extensions/ReplaceText@master] Add lines to composer.json to make it valid
Jul 1 2022
I personally like the idea of installing extensions with Composer (we have to run Composer anyway for some extensions) but I'm not sure this validation issue is the main problem.
I think all MediaWiki extensions should have a valid composer.json. I tagged those projects I could identify as "affected". Not all extensions have a phabricator tag.
Jun 30 2022
I'm going to re-open this ticket because I do think it is both valid, and separate from T250406
composer validate --no-check-publish
In Element chat I raised this same issue. (Sorry for forking the thread.)
Jun 29 2022
We used to add name/description/license/etc. to composer.json with the intent of leaving them unpublished and then people went ahead and published them to packagist anyways, so we had to take them out.
Jun 28 2022
I'm a 3rd-party (corporate) user of MediaWiki and we use Docker for local sandbox development while hosting official environments (DEV, QA, PROD) in AWS using their analog called ECS (Elastic Container Service).
Jun 26 2022
Please use composer validate --no-check-publish.
Jun 25 2022
Jun 24 2022
composer.json files are mainly used for linter and build tools on the CI or to install dependency for all installs, but not to support install of the extension itself, thats why the files are not needed to be valid.
All the information are just duplicated with extension.json and would introduce maintenance burden or going out of sync. No need to have strictly valid files, along there are usable for CI purpose.
Publishing is not required. In fact, you can't publish a package with an invalid composer.json file.
There is no reason why MediaWiki extensions should have invalid composer.json files.