Updating Drush to the Latest Stable Version

Latest Drush Version Default in Use

Drush 13.0.0 was released on Aug 2

• Better Terminal interface

• Able to run recipes using drush

Release 13.0.0 · drush-ops/drushGitHub

More Drush releases followed after that date.

Drush 11 support is end in November 2023

Many options to change to

1. "drush/drush": "~13",

2. "drush/drush": "~12 || ~13",

3. "drush/drush": "~12",

4. "drush/drush": "@stable",

The root composer.json file for the default Varbase Project template was changed "drush/drush": "~13", for easier support, update, and upgrade processes in development and production servers.

Basic Ways to Update Drush

Updating drush in the root composer.json file for a project.

1. Edit the composer.json file

Use any text editor and change to "drush/drush" to the following

    "drush/drush": "~13",

2. Run a Composer Command

composer require "drush/drush:~13" --dev

Varbase Versions and Drush Versions

• Varbase 9.0.4 and older works only with Drush ~10.0

• Varbase 9.0.5 and newer works only with Drush ~11.0

• Varbase 9.0.16 , Varbase 10.0.0-rc1 and newer works only with Drush ~12.0

• Varbase 9.1.5 and older works only with Drush ~12 || ~13

• Varbase 9.1.6 and newer works only with Drush ~13

• Varbase 10.0.0 and older works only with Drush ~12 || ~13

• Varbase 10.0.1 and older works only with Drush ~12 || ~13

• Varbase 10.0.2 and newer works only with Drush ~13

Drush and the Update Helper

The Update Helper ~4.0 is using "drush/drush": "~13" and the Drupal Core Generator package is using "chi-teck/drupal-code-generator": "^3.0"

• Issue #3393654: Updated the Update Helper module from 3.0.4 to 3.0.4 || 4.0.0 to support Drush ~12.0 and kept needed patches

• Issue #3393644: Updated Checklist API module from 2.1.1 to ~2.1.0 and removed committed patches

In require of the module

composer.json · 4.0.x · project / update_helper · GitLabGitLab

Update Helper composer.json file has "drush/drush": "~12.0"

This module has the Drush command. In order to execute it properly, you have to use Drush installed with your project. In the case of composer build, it's: [project directory]/vendor/bin/drush

They started to ask developers to use the drush command. not the one in the global, the one in the vendor.

Drush Use in Varbase

Not recommended to use the local global drush or the server global drush

Use the Direct Drush from Vendor

Change the directory in the terminal to the project directory.

cd [project directory]

Run the following command for example:

./vendor/drush/drush/drush cr

Then command will use the local drush command directly from vender in case the following composer config was not in the root composer.json file for the project

    "bin-dir": "bin/",

Use the Aliased Drush Command From the Bin folder

The default Varbase Project template has the "bin-dir": "bin/",composer config in the root composer.json file.

If the current working directory was the docroot folder in the opened terminal

cd [project directory]/docroot

Run the following command for example:

../bin/drush cr