Updating a Varbase site is no longer a single tool you run and walk away from. The current process is version-specific: you follow the guide for your exact jump, work through it with Composer, Drush, and DDEV, and always in a development environment before production. Across the Drupal 10 to 11 transition, a Varbase update is closer to a migration than a routine patch.
This guide explains what updating Varbase involves now, the durable shape that holds across releases, and where to find the exact commands for your version.
Updating a Varbase site follows a version-specific guide using Composer, Drush, and DDEV, always in a development environment first. The durable shape is: back up, uninstall the modules dropped in the new release, repoint composer.json, run a clean install so patches reapply, run the database updates, then verify. Major jumps across Drupal versions are migrations, not routine patches.
What Changed in How You Update Varbase?
Updating Varbase moved from a single updater tool to documented, version-specific upgrade guides. Older Varbase shipped a helper that ran the update through a wizard.
Current Varbase documents each supported jump as its own guide, with the exact commands for that release, run through a standard Composer, Drush, and DDEV toolchain.
The table below maps the older approach to the current one.
Aspect
Older Varbase (8.x/9, Drupal 9)
Current Varbase (Drupal 11)
How you update
A varbase-updater tool and wizard (update-varbase.sh, varbase-refactor-composer)
A version-specific guide for your exact jump, run with Composer, Drush, and DDEV
Toolchain
Composer on the project
DDEV with PHP 8.4, Composer, Drush, and Yarn for front-end libraries
Patches
Handled by the updater
vardot/varbase-patches reapplied through a full clean composer install
Nature of a major update
Run the tool, follow the wizard
An architecture migration on the Drupal 10 to 11 jump (UI Patterns 1 to 2 Single Directory Components, Gin admin theme, Bootstrap 5)
Automation
Manual wizard
Review-gated AI upgrade agents published by Vardot, run per version
The practical takeaway is that there is no longer one command that fits every site and every version. What updating looks like depends on which release you are moving from and to.
Why Updates Are Now Version-Specific
Varbase publishes a separate upgrade guide for each supported jump because each release drops different modules and changes different configuration.
The current guides cover moving Varbase 9.1 to 9.2 and Varbase 10.0 to 10.1, and both target Drupal 11.4. Each guide lists the modules to uninstall first, the exact composer.json lines to change, and the version-specific configuration migrations to run.
That structure exists because a Varbase update is rarely just a version bump. Varbase 9.2 is a Drupal 11-only release that drops Drupal 10 and removes modules that Drupal 11 removed from core, such as Statistics and Action.
Varbase 10.1 moves the admin theme to Gin, adds an automation stack, and moves the component system from UI Patterns 1 to UI Patterns 2. The steps that make those changes safely are specific to the release, which is why they live in a maintained guide rather than a fixed blog command list.
A Major Varbase Update Is a Migration, Not a Maintenance Task
A major Varbase update is a migration, and treating it like routine maintenance is where upgrades go wrong. On the Drupal 10 to 11 transition, Varbase does not only raise version numbers.
The admin theme moves to Gin, the component system moves from UI Patterns 1 to UI Patterns 2 Single Directory Components, and the front-end theme is Bootstrap 5.
Stored configuration for blog cards and the media hero slider has to be re-provisioned so those elements keep rendering, and your own custom modules and themes are outside the Varbase upgrade entirely.
The failure mode is planning a major update as a quick chore, running the database updates, and finding broken displays and incompatible custom code afterward.
Budget a major Varbase update like a small project: a development environment, a test pass, and time to bring your own code to Drupal 11. The routine, in-line updates within a release are the easy case. The cross-version jumps are the ones to plan for.
How Do You Update a Varbase Site Today?
Update a Varbase site by following the version-specific guide for your jump, in a development environment, with a backup you can restore from. The exact commands differ by release, but the shape below holds across the current guides. Use it to plan the work, and use the matching version guide for the precise commands.
Work in a development environment first. Update and test locally or in staging, then deploy the tested code and build to production. Do not update Varbase directly on production.
Confirm your starting point and back up. Check your current Drupal and Varbase versions, and back up the database and the files directory before you change anything.
Upgrade your own custom code first. The Varbase upgrade covers Varbase, its modules, and its themes. It does not touch your custom modules or custom sub-themes. Run Upgrade Status, set core_version_requirement to ^11, replace removed APIs, re-author custom UI Patterns 1 patterns as Single Directory Components, and move a Bootstrap 4 custom theme to Bootstrap 5.
Uninstall the modules the new release drops, while still on the old version. Doing this while the module code still exists lets Drupal run each module's own clean uninstall, so the later database updates do not stop on a missing module.
Repoint composer.json to the new line. Update the Varbase, patch, and Drupal core scaffold entries to the target versions, and allow the patch plugins to run.
Run a full clean install so patches reapply. Removing the lock file and vendor tree and reinstalling makes Composer resolve from scratch and reapply the curated patch set in one pass, which an incremental update can miss.
Run the database updates and rebuild the cache. Apply the schema and module updates, then clear caches.
Handle the version-specific configuration migrations. Some jumps need extra steps the database updates do not cover, such as remapping card displays to the new Single Directory Components or switching to the new dashboards. The version guide lists these for your release.
Verify. Check the reported versions, confirm the log is clean, and click through the front end and admin pages before you deploy.
Can You Automate a Varbase Upgrade?
Yes, within limits. Vardot publishes upgrade agents in its dev-ai-agents repository that run a specific version jump end to end, for example an agent for the 9.1 to 9.2 upgrade and one for the 10.0 to 10.1 upgrade.
They run the mechanical sequence, uninstall the dropped modules, repoint Composer, reapply patches, run the updates, and verify.
The guardrails matter as much as the automation. These agents work through review-gated merge requests, do not publish a release on their own, and still ask the site owner to upgrade the project's custom modules and themes first.
Automation runs the repeatable steps. It does not remove the need to review, test, and handle the code that is specific to your project.
Where Do You Find the Exact Update Steps?
Use the version-update guide that matches your jump for the exact commands. The current guides cover Varbase 9.1 to 9.2 and Varbase 10.0 to 10.1, and the Updating Varbase section of the documentation also covers configuration handling, patches, Composer, and Drush.
Start from the guide for your source and target versions rather than a generic command list, because the modules to uninstall and the configuration to migrate are specific to each release.
Where to Go Next
If you are planning a Varbase upgrade, start from the version-update guide that matches your current and target versions, and run it in a development environment with a backup in hand. For teams that would rather not run a major upgrade in-house, Vardot handles Varbase and Drupal upgrades as part of ongoing managed services, so the update path, the patch set, and the Drupal 11 migration work are maintained for you.
Planning a Varbase upgrade? Start from the version-update guide that matches your jump, or have Vardot handle it for you.
Abdullah Abu Zakham is a Senior Drupal Developer at Vardot with over 12 years of hands-on experience designing and building web solutions. He specializes in Drupal development, PHP, custom module development, content migration, and performance optimization. Throughout his career, Abdullah has worked on complex, large-scale projects leading development teams, and collaborating with clients to deliver high-quality digital experiences.
Update a Varbase site by following the version-specific upgrade guide for your jump, in a development environment first. Back up the database and files, uninstall the modules the new release drops, repoint composer.json to the new line, run a clean composer install so patches reapply, run drush updatedb, and verify before deploying to production.
No. The current Varbase documentation does not use the older varbase-updater bash tool. Updates now follow a version-specific guide run with Composer, Drush, and DDEV, with the patch set reapplied through a full clean composer install. Use the guide that matches your source and target versions.
No. Update Varbase in a local or development environment first, then deploy the tested code and build to production. Updating directly on production risks breaking the live site, because major updates change modules, configuration, and themes that need to be verified before they go live.
A major Varbase update to Drupal 11 is an architecture migration. The admin theme moves to Gin, the component system moves from UI Patterns 1 to UI Patterns 2 Single Directory Components, and the front end is Bootstrap 5. Stored displays are re-provisioned, and your custom modules and themes must be made Drupal 11-compatible separately.
Partly. Vardot publishes upgrade agents that run a specific version jump end to end through review-gated merge requests, without publishing a release on their own. They run the mechanical steps but still require the site owner to upgrade custom modules and themes and to review and test the result.
