Problem/Motivation
The Varbase profile's composer.json on the 10.1.x branch currently pins:
"drupal/vartheme_bs5": "4.0.x-dev", "drupal/varbase_components": "3.0.x-dev",
A newer vartheme_bs5 4.1.x release now exists (core_version_requirement ~11.4.0). Its own composer.json requires "drupal/varbase_components": "~3.1", not the 3.0.x line currently pinned by the profile. varbase_components 3.1.x is also released and core-compatible (core_version_requirement: ~11.4.0). This profile line is still under active development, so the fix tracks the active 4.1.x/3.1.x development branches rather than pinning stable tagged releases.
Bumping vartheme_bs5 alone without also bumping varbase_components to the version it requires would leave the profile with an internally inconsistent, mismatched pair.
Steps to reproduce
Inspect composer.json on the varbase profile's 10.1.x branch and compare it against vartheme_bs5's 4.1.x composer.json requirement for drupal/varbase_components.
Proposed resolution
Bump both version constraints together in the profile's composer.json, tracking the active 4.1.x/3.1.x development branches (this profile line is still under active development, so dev-branch aliases are used rather than stable tag pins):
"drupal/vartheme_bs5": "4.1.x-dev", "drupal/varbase_components": "3.1.x-dev",
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
- ➖ UX/UI designer responsibilities
- ➖ Accessibility and Readability
- ❌ Reviewed by a human
- ❌ Code review by maintainers
- ❌ Full testing and approval
- ❌ Credit contributors
- ❌ Review with the product owner
- ✅ Update Release Notes
- ✅ Release varbase-10.1.1, varbase_project-10.1.1
User interface changes
- N/A
API changes
- N/A
Data model changes
- N/A
Release notes snippet
- N/A
Issue fork varbase-3609502
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
rajab natshahComment #5
rajab natshahComment #6
rajab natshahComment #7
rajab natshah✅ Released varbase-10.1.1, varbase_project-10.1.1
Comment #8
rajab natshah