PHPackages                             digitalpolygon/drupal-upgrade-plugin - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [DevOps & Deployment](/categories/devops)
4. /
5. digitalpolygon/drupal-upgrade-plugin

ActiveComposer-plugin[DevOps & Deployment](/categories/devops)

digitalpolygon/drupal-upgrade-plugin
====================================

A Composer plugin designed to streamline the process of updating Drupal core installations.

2.0.2-alpha(1y ago)03.6k1[1 issues](https://github.com/digitalpolygon/drupal-upgrade-plugin/issues)1GPL-2.0-or-laterPHPPHP >=7.3.0

Since Mar 1Pushed 11mo ago4 watchersCompare

[ Source](https://github.com/digitalpolygon/drupal-upgrade-plugin)[ Packagist](https://packagist.org/packages/digitalpolygon/drupal-upgrade-plugin)[ Docs](https://www.drupal.org/project/drupal)[ RSS](/packages/digitalpolygon-drupal-upgrade-plugin/feed)WikiDiscussions main Synced 1mo ago

READMEChangelog (4)Dependencies (3)Versions (7)Used By (1)

Drupal Core Composer Updater Plugin
===================================

[](#drupal-core-composer-updater-plugin)

What problem does this plugin actually solve?
---------------------------------------------

[](#what-problem-does-this-plugin-actually-solve)

It removes, or greatly eases, the "Composer dependency hell" phase of upgrading Drupal core. With this plugin, you can run a command that effectively says "This is the version of Drupal core I want to upgrade to, do whatever you need to get me there."

What does this plugin do?
-------------------------

[](#what-does-this-plugin-do)

It provides commands for helping you upgrade Drupal core. It manipulates Composer and effectively wraps `composer update ...`.

By default, when updating, the following flags are passed to the update command:

- `--no-scripts`
- `--no-plugins`
- `--prefer-lowest`

Scripts and plugins are disabled by default in order to avoid interference from other scripts that might otherwise cause the update process to fail (such as Composer patches failing to apply a patch to a new version of a package).

Preferred package versions are their lowest by default. This is done to help minimize validation of other modules that must be updated in order to get to the targeted version of core (i.e. the lowest compatible version of a module will likely have fewer changes compared to higher versions, thus reducing the amount of functionality you need to verify with the new module version).

`--ignore-platform-reqs` can also be configured to pass to the core update command, but this is disabled by default as to ensure platform compatibility remains (doesn't make sense to upgrade to a version of a module the requires PHP 8.3 if your running PHP 8.2). In the future, the update command may default to ignoring platform requirements, as that removes an additional barrier to updating packages purley based on semantic versioning compatibility.

See the configuration section below for more details.

Again, the goal is to improve the chances of successfully updating to the targeted version of core with the least amount of manual intervention possible, which this default configuration helps with the most.

Features
--------

[](#features)

- **Automatic Version Detection**: Easily upgrade to latest major, next major, latest minor, or specific version of Drupal core.
- **Seamless Updates**: Updates core packages with minimal changes to all other packages.
- **Rollback Mechanism**: Provides a safe fallback by backing up your composer files before making any changes.

Installation
------------

[](#installation)

To install the Drupal Core Composer Updater Plugin, follow these steps:

1. Require the package:

    ```
    composer require digitalpolygon/drupal-upgrade-plugin;
    ```
2. Create the manifest file: `/drupal_manifest/composer.json`with all of your Drupal packages (except dev, those must be kept in the root composer.json). You can change 'project/' to your project name and alter version as your project grows.

    Example:

    ```
     {
       "name": "project/drupal-manifest",
       "version": "1.0.0",
       "type": "metapackage",
       "require": {
         "drupal/core-composer-scaffold": "^10.3",
         "drupal/core-project-message": "^10.3",
         "drupal/core-recommended": "^10.3",
         "drupal/search_api": "^1.30",
         "drush/drush": "^12"
       }
     }
    ```
3. Add the following to your `/composer.json` repositories section:

    ```
    {
      "type": "path",
      "url": "./drupal_manifest"
    }
    ```
4. Require the project pacakge you just created:

    ```
    composer require project/drupal-manifest:1.0.0
    ```
5. Run `composer update --lock`.

Going forward, add Drupal packages to the manifest file.

Managing requirements in the manifest
-------------------------------------

[](#managing-requirements-in-the-manifest)

Typically when you add new packages, you use `composer require ...` which will update `composer.json` in your project directory. If you are requiring packages that are not related to Drupal, this is fine, but if you are requiring a Drupal package then it is highly recommended that this goes in the manifest file. There are two methods for doing this:

### Modify requirements from the command line

[](#modify-requirements-from-the-command-line)

```
composer require drupal/foo:^1.2 --working-dir=drupal_manifest --no-update
composer update drupal/foo
```

### Manually modify requirements

[](#manually-modify-requirements)

Edit the `drupal_manifest/composer.json` file directly:

```
{
  "name": "project/drupal-manifest",
  "type": "metapackage",
  "require": {
    "drupal/core-composer-scaffold": "^10.3",
    "drupal/core-project-message": "^10.3",
    "drupal/core-recommended": "^10.3",
    "drupal/search_api": "^1.30",
    "drush/drush": "^12",
    "drupal/foo": "^1.2"
  }
}
```

Then run:

```
composer update drupal/foo
```

Usage
-----

[](#usage)

To update your Drupal core to a new version, run the following command in your project root:

```
composer drupal:core:version-change 10.3.1;
```

This command will attempt to update all Drupal core packages to 10.3.1 and also attempt to update any other package in the manifest to a version that would be compatible with Drupal 10.3.1 (regardless of the constraints you currently have specified in the manifest).

### Usage with Flags

[](#usage-with-flags)

Instead of specifying a specific version, you can specify one of the following flags to dynamically calculate the version to update to:

2. `--latest-minor`: Update to the latest stable minor version within the currently installed major version of Drupal core.
3. `--latest-major`: Update to the latest stable major version of Drupal core. This option will upgrade your site to the latest available version of Drupal.
4. `--next-major`: Update to the latest stable of the next major version of Drupal core.

Configuration
-------------

[](#configuration)

The plugin can be configured via the extra section of `composer.json` file in your project root. All configuration options are optional. The values specified below are the defaults:

```
{
    "extra": {
        "drupal-upgrade-plugin": {
            "ignore-platform-reqs": false,
            "include-root-dependencies": false,
            "prefer-lowest": true,
            "no-scripts": true,
            "no-plugins": true,
            "manifest-file": {
                "path": "./drupal_manifest",
                "name": "project/drupal-manifest"
            },
            "packages-linked-to-core-version": [
                "drupal/core-composer-scaffold",
                "drupal/core-project-message",
                "drupal/core-recommended",
                "drupal/core-dev",
                "drupal/core"
            ]
        },
    }
}
```

**ignore-platform-reqs**

Set to `true` to ignore platform requirements when updating packages.

**include-root-dependencies**

Set to `true` to allow updates of packages in the root composer.json.

**prefer-lowest**

Set to `true` to prefer the lowest version of packages that satisfy the constraints.

**manifest-file.path**

The path to the manifest file repository.

**manifest-file.name**

The name of the manifest file package.

**packages-linked-to-core-version**

A list of packages that share their versioning with Drupal core.

**no-scripts**

Set to `true` to disable scripts during the update process.

**no-plugins**

Set to `true` to disable plugins during the update process.

Contributing
------------

[](#contributing)

We welcome contributions to enhance the functionality and features of this plugin. Please fork the repository and submit pull requests for any improvements or bug fixes.

###  Health Score

28

—

LowBetter than 54% of packages

Maintenance48

Moderate activity, may be stable

Popularity22

Limited adoption so far

Community14

Small or concentrated contributor base

Maturity23

Early-stage or recently created project

 Bus Factor1

Top contributor holds 95.8% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~7 days

Total

4

Last Release

420d ago

Major Versions

1.0.0-beta1 → 2.0.0-alpha12025-03-22

### Community

Maintainers

![](https://www.gravatar.com/avatar/85e23fca128aed0b404f899ab0ada6eef6d0fe8abd3635ce4f2522d25aa42cda?d=identicon)[lpeabody](/maintainers/lpeabody)

---

Top Contributors

[![lpeabody](https://avatars.githubusercontent.com/u/419534?v=4)](https://github.com/lpeabody "lpeabody (23 commits)")[![maarten-digitalpolygon](https://avatars.githubusercontent.com/u/182478614?v=4)](https://github.com/maarten-digitalpolygon "maarten-digitalpolygon (1 commits)")

---

Tags

plugincomposerdrupalcore upgrader

### Embed Badge

![Health badge](/badges/digitalpolygon-drupal-upgrade-plugin/health.svg)

```
[![Health](https://phpackages.com/badges/digitalpolygon-drupal-upgrade-plugin/health.svg)](https://phpackages.com/packages/digitalpolygon-drupal-upgrade-plugin)
```

###  Alternatives

[ergebnis/composer-normalize

Provides a composer plugin for normalizing composer.json.

1.1k37.3M2.1k](/packages/ergebnis-composer-normalize)[sllh/composer-lint

Extends the composer validate command with extra rules

14214.6k7](/packages/sllh-composer-lint)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)