You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 6, 2022. It is now read-only.
Now we provide strict composer versions in order to prevent issues when backend module has updates that aren't suitable to old frontend, but we don't have ability to update frontend.
But now if i want to update backend module on purpose, i get this error when i start theme:
The 3.1.28 version is the minimum requested version.
Update it at you own risk! The version of choice must meet following constraints: 3.1.28!
While in the same time i have 3.1.31 installed by composer.
The composer version checking code should compare and allow package versions if they are greater.
Also it would be nice to output all conflicting versions on the same screen, than check versions one by one and stop on the first conflict.
The text was updated successfully, but these errors were encountered:
Now we provide strict composer versions in order to prevent issues when backend module has updates that aren't suitable to old frontend, but we don't have ability to update frontend.
But now if i want to update backend module on purpose, i get this error when i start theme:
While in the same time i have 3.1.31 installed by composer.
The composer version checking code should compare and allow package versions if they are greater.
Also it would be nice to output all conflicting versions on the same screen, than check versions one by one and stop on the first conflict.
The text was updated successfully, but these errors were encountered: