In the Test tab, you’ll see a highlighted section detailing what commits are ready to be tested against the live site.
All the checkboxes should be selected, and you can add a Deploy Log Message if you’d like.
If the minor version number is any more than one, or if the major version has changed, it’s good practice to check the release notes on (a link is provided next to the Recommended Version number, as shown in Figure 4).
Once you’ve selected the modules you’d like to update, click the ‘Download these updates’ button and let Drupal do the rest.
Recently, we were helping a client get their Drupal 8 website set up for hosting on the Pantheon platform.
They would eventually take over updates of both core and contrib modules for the site.
Because 1.17 is out, 1.15 (the last one that worked before the breaking change) no longer matches the version constraints in our file, so if we want it, we'll have to specify the version manually.I'll explain more about why that is in another video, but let's get to it.I'll install Admin Toolbar since it has multiple releases that we can move through.Now, as I mentioned before, it's actually not best practice to include a specific version number.
The most common version pattern I use is the one that begins with the "^" (caret) symbol I need to downgrade because of a breaking change with the latest release.You'll notice that even though I used the version "1.0", Composer installed version 1.17.