Skip to main content
Log inGet free account

Update Your Project

In step nine of the Build Tools guide, learn how to update your site as part of the continuous integration process.

Discuss in Slack
Edit this page on GitHub Report an issue with this doc

In this lesson, we'll take a closer look at how to update dependencies in a Composer workflow.

Composer

Composer Fundamentals

Composer is a PHP dependency manager that provides an alternative, more modern way to manage the external code used by a WordPress or Drupal site. At its primary level, Composer needs:

  • A list of dependencies
  • A place to put the dependencies

Understanding how Composer can be used independent of Drupal or WordPress is a good place to learn more about the general concepts. For a summary of basic usage, see Composer's own documentation.

Automation Training

Learn Composer concepts with help from our experts. Pantheon delivers on-demand training to help development teams navigate the platform and improve internal WebOps.

Learn more

Dependencies

Composer encourages a mental model where code not written specifically for a given project is a dependency. Only files unique to the project are tracked as part of the project's main source repository, also referred to as the canonical site repository. Dependencies for WordPress and Drupal include core, plugins, contrib modules, themes, and libraries. A single dependency, such as a theme, is referred to as a package.

Composer looks within The PHP Package Repository for dependencies to install, which does not include Drupal or WordPress packages by default. Additional repositories must be configured for Composer to use packages not found in the default repository. Each framework provides it's own respective package repository so dependencies can be managed with Composer:

Sites created from Pantheon's example repositories already include the appropriate package repository within the composer.json file.

repositories": [
     {
       "type": "composer",
       "url": "https://packages.drupal.org/8"
     }
   ],

Update Core

  1. Start by creating a new branch based off the tip of master (replace drupal-8.3.7 according to your current task):

    git checkout -b drupal-8.3.7 master

  2. Update your project to the current Drupal stable version of core released on drupal.org with Composer:

    composer update drupal/core

  3. Run git diff composer.lock to see the updated dependency details:

    composer diff core

  4. Commit the updated composer.lock file and push a new branch up to GitHub, for example (replace drupal-x.x.x according to your current task):

    git commit -m="Update to Drupal x.x.x"
  git push origin drupal-x.x.x

  5. Return to GitHub and compare your feature branch against master. You should see all commits made locally here in GitHub. Click Create Pull Request and go through your team's standard peer review process.

Use this process to update any dependency required by your project's composer.json file. The site should never receive Pantheon's one-click updates in the Pantheon Site Dashboard, Drupal's Admin interface, or Drush to update core, as none of these techniques modify the composer.json file. You must update core using Composer exclusively.