vardot/varbase-patches

List of needed patches for Varbase used packages with Composer Patches.

11.0.24 2026-07-14 15:15 UTC

Requires

• php: >=8.1
• composer-plugin-api: ^2.0
• composer/installers: ~2
• cweagans/composer-patches: ~1.7.0 || ~2.0
• oomphinc/composer-installers-extender: ~2
• vardot/drupal-core-patches: ~11 || ~12

GPL-2.0-or-later

• Vardot

• composer
• drupal
• patches
• varbase
• drupal patches
• composer patches
• varbase patches

Published on Packagist.org on 2026-07-14 15:27 UTC

README

List of needed patches for Varbase used packages with Composer Patches.

The 11.0.x branch tests itself: it installs Drupal plus the modules it patches, asserts that Composer Patches applies all of them, and checks that every patch file still exists (tests/).

Composer plugin and curated patch list for Varbase. Built on top of cweagans/composer-patches v2 with three additions that v2 dropped or never had:

• Wildcard ignore-dependency-patches (e.g. drupal/*).
• Allowlist allowed-dependency-patches — only listed packages contribute dependency-declared patches. Defaults to ["vardot/varbase-patches"].
• patches-ignore restored from cweagans v1 — drop a specific URL declared by a given dependency.

Plus two Composer commands to convert remote merge-request URLs into local timestamped patch files (./patches/<package>--YYYY-MM-DD--<issue>--mr-<n>.patch).

Quick start

composer require vardot/varbase-patches:~11.0.0

{
  "config": {
    "allow-plugins": {
      "cweagans/composer-patches": true,
      "vardot/varbase-patches": true
    }
  },
  "extra": {
    "enable-patching": true,
    "composer-exit-on-patch-failure": true,
    "composer-patches": {
      "allowed-dependency-patches": [
        "vardot/varbase-patches",
        "vardot/drupal-core-patches"
      ]
    },
    "patches": {}
  }
}

composer install

Result: only patches declared by vardot/varbase-patches (and your project's own extra.patches) apply. Patches declared by other dependencies are skipped — no more aborted installs from stale third-party .patch URLs.

Versions

Branch	Drupal core	Use with
11.0.x	~11.3.0	Varbase ~11.0.0, Drupal 11
10.1.x	~11.3.0	Varbase ~10.1.0
10.0.x	~10.6.0	Varbase ~10.0.0
9.2.x	~10.6.0	Varbase ~9.2.0
9.1.x	~10.6.0	Varbase ~9.1.0
no-patches	n/a	Plugin only, manage your own list

The patches branch carries patch files only — do not require it.

Drupal Core Patches

Drupal core patches are managed in a dedicated package, vardot/drupal-core-patches, so Varbase can always track the latest Drupal core release while keeping core patches separate from contrib patches.

vardot/varbase-patches requires vardot/drupal-core-patches. The core-patches package stores the curated Drupal core patches with one git branch per Drupal core major.minor — 10.4.x, 10.5.x, 10.6.x, 11.1.x, 11.2.x, 11.3.x, 11.4.x, 12.0.x — plus a flat patches branch that holds the actual .patch files. Each drupal-core-patches release requires drupal/core ~<minor>.0, so Composer automatically selects the patch set that matches the Drupal core version installed in your project.

On this branch vardot/varbase-patches requires:

{
  "require": {
    "vardot/drupal-core-patches": "~11 || ~12"
  }
}

Note: vardot/drupal-core-patches is a metapackage — a storage for Drupal core patches — not a Composer plugin. The only Varbase patch plugin is vardot/varbase-patches. List vardot/drupal-core-patches only under extra.composer-patches.allowed-dependency-patches, and never under config.allow-plugins.

Composer commands

The plugin registers two Composer commands to convert remote GitLab merge-request URLs in your patch lists into local timestamped .patch files under ./patches/. They replace the Drush commands previously shipped in varbase_core (see docs/migration-from-drush.md).

Clean up the root composer.json file

• Name: varbase-patches:cleanup:patches
• Aliases: var-ccup
• Description: Detects any merge request patches in the root composer.json extra.patches block, downloads them to the local ./patches/ folder with a timestamped filename, and updates the root composer.json to use the local patch file.

composer varbase-patches:cleanup:patches

or

composer var-ccup

Clean up the external patches-file JSON file

• Name: varbase-patches:cleanup:patches-file
• Aliases: var-ccupf
• Description: Detects any merge request patches in the JSON file referenced by extra.patches-file, downloads them to the local ./patches/ folder with a timestamped filename, and rewrites the patches-file JSON to use the local patch file.

composer varbase-patches:cleanup:patches-file

or

composer var-ccupf

Handling Varbase Patches Ignoring

To exclude a specific patch declared by vardot/varbase-patches (e.g. when you want to replace it with an improved version, or skip it entirely), add a patches-ignore block to your root composer.json:

{
  "extra": {
    "patches-ignore": {
      "vardot/varbase-patches": {
        "drupal/recaptcha": {
          "fix: #3588269 Make Drupal8Post::submit() compatible with parent":
          "https://git.drupalcode.org/project/recaptcha/-/commit/68b0f86d1e930ed78f795a97a2fc207be35b3260.diff"
        }
      }
    }
  }
}

Schema: { "<source-pkg>": { "<target-pkg>": { "<description>": "<url>" } } }. Matching is done by URL — the description string is informational. A flat array of URLs ({ "<source-pkg>": { "<target-pkg>": ["<url>", ...] } }) is also accepted.

This is the v1-style patches-ignore from cweagans/composer-patches, restored by this plugin on top of v2.

Ignoring Drupal Core Patches

vardot/drupal-core-patches is an ordinary dependency that contributes patches through the dependency resolver, so the same patches-ignore block controls it — use vardot/drupal-core-patches as the source package and drupal/core as the target:

{
  "extra": {
    "patches-ignore": {
      "vardot/drupal-core-patches": {
        "drupal/core": {
          "Issue #3606822: ContainerBuilder synthetic kernel on install": "https://git.drupalcode.org/project/drupal/-/merge_requests/16159.patch"
        }
      }
    }
  }
}

Matching is by URL string, the same as for vardot/varbase-patches.

Filename convention

[package name]--[Date]--[issue number]--[MR number].patch

Examples:

• drupal-core--2026-05-10--3539178--mr-12890.patch
• ctools--2026-05-10--3572317--mr-85.patch
• redirect--2026-05-10--2879648--mr-109.patch

Documentation

• Overview
• Installation
• Configuration
• Commands
• Architecture
• Migration from Drush
• Troubleshooting

External: https://docs.varbase.vardot.com/developers/varbase-patches

AI assistant context

This repository ships its own AI-assistant context so contributors get the same project conventions as core maintainers:

• AGENTS.md — vendor-neutral entry point. Works with any AI coding assistant (Claude Code, Cursor, Codex, Aider, Continue.dev, Copilot Workspace, …).
• CLAUDE.md — Claude Code-specific entry point.
• .claude/agents/varbase-patches.md — Claude sub-agent.
• .claude/skills/composer-patches/SKILL.md, .claude/skills/patch-management/SKILL.md — Claude skills.

Requirements

• PHP >=8.1
• composer-plugin-api ^2.0
• cweagans/composer-patches ~2.0

License

GPL-2.0-or-later. See LICENSE.

Maintainer

Vardot — https://github.com/vardot