Closed krabina closed 4 years ago
Also, mermaid 2.2.2 is not compatible with MW 1.31 afaik, so it should say it needs at least MW 1.33...
Here applies the same comment as in https://github.com/SemanticMediaWiki/SemanticResultFormats/issues/570#issuecomment-599029961.
It happend to me twice that an update of a MW installation where Mermaid was NOT installed, resulted in updating mermaid to 2.2.0:
How can it update mermaid from 2.1.1 to 2.2.2 if my composer.local.json looks like this:
Mermaid was indeed installed before, since it was required via SRF.
In case you would like to avoid this you explicitly have to add "mediawiki/mermaid": "2.1.0"
to your "composer.local.json" file.
Also, mermaid 2.2.2 is not compatible with MW 1.31 afaik, so it should say it needs at least MW 1.33...
Well, MediaWiki complains about this. Still it will indeed be nicer if the software was not updated in the first place. Dunno if this can be done with Composer since MW itself is not installed via Composer.
Anyhow we now have a pull-request to make this situation better: https://github.com/SemanticMediaWiki/SemanticResultFormats/pull/574 Thus closing here.
Setup and configuration
Issue
It happend to me twice that an update of a MW installation where Mermaid was NOT installed, resulted in updating mermaid to 2.2.0:
How can it update mermaid from 2.1.1 to 2.2.2 if my composer.local.json looks like this:
Also, mermaid 2.2.2 is not compatible with MW 1.31 afaik, so it should say it needs at least MW 1.33...