Upgrade to varbase 10.1.0? (and from Drupal 10 to Drupal 11?)

Thanks Gabriele for asking

The use of /bin/update-varbase.sh only was used in Varbase ~9 .
Varbase 10.0.x did not use it.

Support for Varbase 10.0.x will stop in 3 months.
( All Varbase ~10.0.0 projects should update to Varbase ~10.1.0 when upgrading to Drupal ~11.3 )

Updating the documentation for sure. Work in Progress: with post release testing.

Yes, Basic composer update with follow up changes.

Now you can prompt the AI CLI to help you with that
( in a local DDEV/Docker sandbox )

Example #1 Letting the AI do the Basic composer update for a local DDEV/Docker Varbase Project

claude --permission-mode bypassPermissions """
Keep in a loop until you finish the update to Varbase ~10.1.0 in this Varbase project 
- Only working in the /var/www/html/dev/v10x00xsite folder not other folders in the system
- Only configure the DDEV not the local system
- Read the change logs from https://raw.githubusercontent.com/Vardot/varbase/refs/heads/10.1.x/CHANGELOG.md and https://raw.githubusercontent.com/Vardot/varbase/refs/heads/10.0.x/CHANGELOG.md do a deep thinking and research on what added/changed/removed/updated and follow up with what was changed in code and in the linked issues.
- Use DDEV and backup the database before changes to be able to restore it when the update fail.
- Change drupal/core-composer-scaffold to ~11 in the root composer.json
- Change drupal/core-project-message to ~11 in the root composer.json
- Change vardot/varbase to ~10.1.0
- Change vardot/varbase-patches to ~10.1.0
- Add the Component Libraries: Theme Server module drupal/cl_server the ~2.0 with any needed patch to support Drupal ~11.3.0
- Add the drupal/cl_components module with any needed patch to support Drupal ~11.3.0
- Delete the composer.lock file before doing any composer update or composer install
- Enable the ui_patterns_legacy module to support all UI Patterns Legacy components ( the ui_patterns_legacy module is a sub-module in the ui_patterns module) 
- Do not update anything in Vartheme BS5, change for changes in the theme if it was a custom theme ( mytheme for this project ) do not edit vartheme_bs5
- Any still enabled module but was removed from varbase ~10.1.0, add it back in the root composer.json for this project
- Keep the use of UI Patterns legacy in the UI Patterns ~2.0  and keep the view mode with the components  if the are custom in my old theme
- Check the https://project.pages.drupalcode.org/ui_patterns/2-authors/3-migration-from-UIP1 link for more info.
- Switch from using Varbase Dashboards ~1.0 to ~2.0 and migrate the dashboards to use dashboard and add the Navigation Dashboard block to the Navigation Side bar ( Change that the Navigation Dashboard block is in the Navigation Side bar, and when you click on it it will redirect to the default dashboard ) do not add varbase_dashboard ~2.0 as it is in varbase ~10.1.0
- Run the Varbase Dashboards default recipe to make sure that all default configs for the dashboard are imported like dashboard.dashboard.dashboard.yml
- make sure When I go to the /admin/dashboard I should see the Dashboard
- Add the drupal/dashboards module while updating
- run ddev drush en dashboard to install the dashboard module and make
- Uninstall the dashboards module with ddev drush pm:uninstall then remove it form the root composer.json file 
- You are allowed to run ddev drush config:export ; then do your quick config fixes then run ddev drush config:import
- Update Varbase from ~10.0.0 to ~10.1.0
- run ddev drush updb and make sure that all updated worked well without errors
- Bring in any still enabled and used contrib modules in this Varbase project ( add them to the root composer.json ) file.
- Create an automated functional testing with playwright to test the site ( use the ready tests if they are in the project )
- Use the the local DDEV domain "http://v10x00xsite.ddev.site" with username: webmaster and password: dD.123123ddd
- Create playwright automated functional tests to check the most on 200 important back-end pages ( for errors and warnings for Drupal ~11.3.0 or PHP 8.4 )
- Create playwright automated functional tests to check on all front-end pages ( for errors and warnings )
- Check Drupal ~11.3.0 and PHP 8.4 compatibility for all custom required modules ( you are allowed to add a patch, do not change the code )
- Check Drupal ~11.3.0 and PHP 8.4 compatibility for all custom coded modules in docroot/modules/custom ( you are allowed to change the code do not patch )
- Check Drupal ~11.3.0 and PHP 8.4 compatibility for all custom coded themes in docroot/themes/custom ( you are allowed to change the code do not patch )
- If you needed to create patch for a module, create it and save in the local patches folder and add it to the composer.json
- Make sure that composer update is working after you finish all fixes
- Stop when no errors or warnings and the site is Drupal ~11.3.0 and PHP 8.4 compatible
"""

Also

Officially paved the way for Automatic Updates in Varbase projects.

Example #2 Letting the AI enable Automatic Updates a local DDEV site using the guide in 10.1.x

claude --permission-mode bypassPermissions """
Keep in a loop untile you finish Enabling Automatic Updates in this Varbase project 
- keep working only in the /var/www/html/test/v10x00xsite folder
- Only configure the DDEV not the local system
- Using https://docs.varbase.vardot.com/10.1.x/developers/updating-varbase/enabling-automatic-updates guide
- Stop when no errors or warnings
- Check if the site will be able to update with automatic updates
"""

Following with the Example #1, and the documentation will follow with that too

It has been continually confusing that the update document for Varbase has continued to say that the way to update is to use the update-varbase.sh script even in the current releases.

Deprecated the use of update-varbase.sh in Varbase 9
It was never used in Varbase 10

Officially paved the way for Automatic Updates in Varbase projects.

My point actually was that the update.md file in the distro still says to update using the update-varbase.sh script and that the docs should be changed to reflect current practice.

Thanks Steve for the point. ( Got that from the first comment ).

It was changed in https://git.drupalcode.org/project/varbase/-/blob/10.0.x/UPDATE.md
You are right it was not changed yet in the https://git.drupalcode.org/project/varbase/-/blob/10.1.x/UPDATE.md