Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
- #3484597: Start a 3.0.x branch for Varbase Components to support UI Patterns ~2.0 and Storybook and pave the way for a smooth upgrade process to Drupal 11
- #3484616: Start a 4.0.x branch for Vartheme BS5 to support UI Patterns ~2.0 and Storybook, and pave the way for a smooth upgrade process to Drupal 11
UI Patterns (SDC in Drupal UI) ~2.0 stable is nearly out.
Thanks, UI Suite Initiative ( Pierre, Michael, Florent, and all contributors )
Storybook 1.0.0 stable was released on: 10 Sep 2024 by: e0ipso
https://www.drupal.org/project/storybook/releases/1.0.0
Thanks, Mateu
Proposed resolution
- Start a new
10.1.xbranch for the Varbase Profile. - Switch Varbase modules to use a new
10.1.x-devdevelopment branches. - Remove Vartheme Claro as it was deprecated from the
composer.jsonfile.
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
- ✅ 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-10.1.0-alpha1
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 #3484640: Started a
10.1.xbranch for Varbase to support UI Pattern ~2.0, Storybook, and pave the way for a smooth upgrade process to Drupal 11
| Comment | File | Size | Author |
|---|---|---|---|
| #31 | Component-Libraries-Theme-Server-Drupal-org-03-10-2025_12_45_PM.png | 161.4 KB | rajab natshah |
| #9 | 3484640-9.patch | 510 bytes | rahaf albawab |
Issue fork varbase-3484640
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:
- 3484640-start-a-10.1.x
changes, plain diff MR !33
Comments
Comment #2
rajab natshahComment #3
rajab natshahComment #5
rajab natshahComment #6
rajab natshahComment #9
rahaf albawab commentedHi @rajab.
I also noticed a conflict: varbase_layout_builder requires drupal/varbase_editor ~10.1.0 || 10.1.x-dev, but this conflicts with your root composer.json requirement (10.0.x-dev).
Comment #15
pdureau commentedHello you,
You can get some help from https://www.drupal.org/project/sdc_devel which is providing a drush command and a report page.
Still in alpha phase, there are still false positive, unclear messages and some missing warnings, but already very useful to get and fix most of the SDC component authoring errors.
Comment #16
rajab natshahThanks, Pierre, for the hint and for stopping by!
I’ve definitely planned to add your SDC Devel module to Varbase Core and the default set of enabled modules for development in Varbase Development.
We need it for sure
Our team is in the process of migrating all components to work with UI Patterns ~2.0 and Storybook.
To use them in (Layouts, View modes, field formmaters , and Layout Builder ).
Hoping for a pre-release tag (
1.0.0-alpha1)#3499885: Add SDC Devel module to the default Varbase Development recipe
Comment #30
jjwfcd commentedI am waiting for the drupal 11 version for varbase and many varbase modules
today I tried varbase_heroslider on a drupal-cms installation
but
Problem 1
- drupal/cl_components[1.0.0-alpha1, ..., 1.0.0-beta4] require drupal/core ^8 || ^9 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev] but the package is fixed to 11.1.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- drupal/cl_components[dev-1.x, 1.0.0-beta5, ..., 1.x-dev] require drupal/core ^8 || ^9 || ^10 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.5.x-dev] but the package is fixed to 11.1.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- drupal/varbase_components[2.0.0-alpha1, ..., 2.0.0-alpha8] require drupal/core ^10.1 -> found drupal/core[10.1.0-alpha1, ..., 10.5.x-dev] but the package is fixed to 11.1.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- drupal/varbase_components[2.0.0-alpha9, ..., 2.0.0-alpha28] require drupal/core ~10.1.0 -> found drupal/core[10.1.0-alpha1, ..., 10.1.x-dev] but the package is fixed to 11.1.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- drupal/varbase_components[2.0.0-alpha29, ..., 2.0.1] require drupal/core ~10 -> found drupal/core[10.0.0-alpha1, ..., 10.5.x-dev] but the package is fixed to 11.1.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- drupal/varbase_components[2.0.2, ..., 2.0.7] require drupal/core ~10.3.0 || ~11.0.0 -> found drupal/core[10.3.0-beta1, ..., 10.3.x-dev, 11.0.0-alpha1, ..., 11.0.x-dev] but the package is fixed to 11.1.4 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- drupal/varbase_components 2.0.8 requires league/commonmark ~2.4.0 -> found league/commonmark[2.4.0, ..., 2.4.x-dev] but the package is fixed to 2.6.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- drupal/varbase_heroslider 1.0.0-rc1 requires drupal/varbase_components ~2 -> satisfiable by drupal/varbase_components[2.0.0-alpha1, ..., 2.0.x-dev].
- drupal/varbase_components[2.0.9, ..., 2.0.x-dev] require drupal/cl_components ~1 -> satisfiable by drupal/cl_components[1.0.0-alpha1, ..., 1.x-dev].
- Root composer.json requires drupal/varbase_heroslider ^1.0@RC -> satisfiable by drupal/varbase_heroslider[1.0.0-rc1].
so I guess there might be many days to wait before we can use those amazing varbase modules on Drupal 11
thank you guys for your great job
Comment #31
rajab natshahThanks, jueju, for following up.
Use the newer Storybook module to integrate with Storybook. This module will let you put any arbitrary Twig code in your Storybook stories, including Single Directory Components.
With that, we are working on #3484597: Start a 3.0.x branch for Varbase Components to support UI Patterns ~2.0 and Storybook and pave the way for a smooth upgrade process to Drupal 11
Removed using any
cl_modules in Varbase Components.Moving with 100% use of the UI Patterns, following with the UI Suite Initiative.
Varbase 10.1.x will be the right move for Drupal 11 + Storybook ~2.0 + UI Patterns ~2.0
Comment #32
rajab natshahComment #33
rajab natshahComment #34
rajab natshah--
Comment #35
rajab natshah✅ Released varbase-10.1.0-alpha1