Problem/Motivation
Having mixed composer requirements opens the way to get older plugins and libraries
This brings a number of issues to new builds and the autoloader.
#3301451: Have drupal-scaffold locations web-root for Varbase as docroot to fix composer web-root folder in projects
#3302442: Drop support for Composer ~1.0 in Varbase profile and only support Composer ~2.0 and later versions
Proposed resolution
- Ditch the support for Composer
~1.0and older plugins and libraries - Support Composer
~2.0and later versions (~2.1.0,~2.2.0,~2.3.0)
Remaining tasks
- ✅ File an issue about this project
- ✅ Addition/Change/Update/Fix to this project
- ✅ Testing to ensure no regression
- ➖ Automated unit/functional testing coverage
- ✅ Developer Documentation support on feature change/addition
- ➖ User Guide Documentation support on feature change/addition
- ➖ Accessibility and Readability
- ✅ Code review from 1 Varbase core team member
- ✅ Full testing and approval
- ✅ Credit contributors
- ✅ Review with the product owner
- ✅ Update Release Notes and Update Helper on new feature change/addition
- ✅ Release varbase-9.0.8, vartheme_bs4-9.0.16
Varbase update type
- ✅ No Update
- ➖ Optional Update
- ➖ Forced Update
- ➖ Forced Update if Unchanged
User interface changes
- N/A
API changes
- N/A
Data model changes
- N/A
Release notes snippet
- Issue #3302435: Dropped support for Composer
~1.0in the Vartheme BS4 theme and only support Composer ~2.0 and later versions
Comments
Comment #2
rajab natshahComment #3
rajab natshahComment #5
rajab natshahComment #6
rajab natshahComment #7
rajab natshahComment #8
rajab natshahComment #9
rajab natshah✅ Released vartheme_bs4-9.0.16
Comment #10
rajab natshah✅ Released varbase-9.0.8
Comment #11
rajab natshah