- Issue created by @DamienMcKenna
I think the best solution is to create a new 2.0.x branch and change the core requirement to
^10.3 || ^11.0
, then create a new release (1.0.1-alpha5) with deprecations and version constraints rolled back to^9.3 || ^10
.-
tonytheferg β
committed ca869d33 on 2.0.x
Issue #3503806 by damienmckenna: Update module's requirements
-
tonytheferg β
committed ca869d33 on 2.0.x
Automatically closed - issue fixed for 2 weeks with no activity.