Since auto migration, the version 2.2.x of plugin news is no more compatible with version less than 4.3.x.
So the commit was merged to 4.2.x but it is not used, unless we do a branch for 2.1.x version. I don't know if it is necessary for this ticket... I will say no.
Laurence Aumeunier
added a comment - Since auto migration, the version 2.2.x of plugin news is no more compatible with version less than 4.3.x.
So the commit was merged to 4.2.x but it is not used, unless we do a branch for 2.1.x version. I don't know if it is necessary for this ticket... I will say no.
Currently, plugin news is compatible with Runtime 4.0
So, the commit in Runtime should be backported to 4.2
And the plugin news should now be compatbile with >= 4.2 (instead of >= 4.0) (as we no longer support 4.0 and 4.1)
Simon Prieul (Inactive)
added a comment - Currently, plugin news is compatible with Runtime 4.0
So, the commit in Runtime should be backported to 4.2
And the plugin news should now be compatbile with >= 4.2 (instead of >= 4.0) (as we no longer support 4.0 and 4.1)
Since auto migration, the version 2.2.x of plugin news is no more compatible with version less than 4.3.x.
So the commit was merged to 4.2.x but it is not used, unless we do a branch for 2.1.x version. I don't know if it is necessary for this ticket... I will say no.