- Issue created by @Rajab Natshah
-
Rajab Natshah β
committed 428b0fe7 on 10.0.x
Issue #3437221: Switch to a local patching system using vardot/varbase-...
-
Rajab Natshah β
committed 428b0fe7 on 10.0.x
-
Rajab Natshah β
committed 37b73277 on 9.1.x
Issue #3437221: Switch to a local patching system using vardot/varbase-...
-
Rajab Natshah β
committed 37b73277 on 9.1.x
- Issue was unassigned.
- Status changed to Needs review
9 months ago 3:56pm 2 April 2024 -
Rajab Natshah β
committed 4c893d4d on 9.1.x
Issue #3437221: Switch to a local patching system using vardot/varbase-...
-
Rajab Natshah β
committed 4c893d4d on 9.1.x
-
Rajab Natshah β
committed f5f3e1c0 on 10.0.x
Issue #3437221: Switch to a local patching system using vardot/varbase-...
-
Rajab Natshah β
committed f5f3e1c0 on 10.0.x
- Status changed to Fixed
9 months ago 1:30pm 4 April 2024 - πΊπΈUnited States jedgar1mx Detroit
I'm unable to upgrade to `9.1.32`. It looks like there is a conflict between `varbase_core` and `vartheme_bs5` they required different version of `varbase-patches`
- π―π΄Jordan Rajab Natshah Jordan
Thanks, Edgar, for reporting.
Let us do this in the Vartheme BS5 project
The theme was built to work with Varbase10
But we can let it work with Varbase9.1.x
too
By adding"vardot/varbase-patches": "~9.1.0 || ~10.0.0"
, But that may follow up to Varbase Components too
Which version of Vartheme BS5 you are using?Please, file a new issue in Vartheme BS5 and Varbase Components if needed? and let us continue the conversion and the allow to use option.
Automatically closed - issue fixed for 2 weeks with no activity.