Allow Varbase Components ~2 in VMI 3.0.x, so it does not require a dev branch

Problem/Motivation

#3607783 changed drupal/varbase_components from ~2 to 2.x-dev, and 3.0.6 shipped with it. No branch matches 2.x-dev, so Composer cannot install 3.0.6. The 3.0.x branch now says 2.0.x-dev, so 3.0.7 would install only with a dev branch of Varbase Components, on every Varbase 10.0 site (Varbase Core 10.0.x requires drupal/vmi:~3).

Varbase Components 2.0.17 is stable and declares the same core range as the 2.0.x branch, ~10.6.0 || ~11.3.0.

Steps to reproduce

Require drupal/vmi:3.0.6 with drupal/core:~10.6.0:

drupal/vmi 3.0.6 requires drupal/varbase_components 2.x-dev -> found drupal/varbase_components[dev-1.0.x, dev-2.0.x, ...] but it does not match the constraint.

Require drupal/vmi:3.0.x-dev with drupal/core:~10.6.0, "minimum-stability": "dev" and "prefer-stable": true, as Varbase projects do. Composer locks drupal/varbase_components (dev-2.0.x b659f24), not 2.0.17.

Proposed resolution

Go back to ~2, as in 3.0.5.

Remaining tasks

• ✅ File an issue
• ✅ Addition/Change/Update/Fix
• ✅ Testing to ensure no regression
• ➖ Automated unit/functional testing coverage
• ➖ Developer Documentation support
• ➖ User Guide Documentation support
• ➖ 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

User interface changes

• N/A

API changes

• N/A

Data model changes

• N/A

Release notes snippet

• VMI 3.0.x requires stable Varbase Components 2.0 releases again, not a dev branch.

AI-Generated: Yes