Install

Works with Drupal: ^11.1 || ^12

Using Composer to manage Drupal site dependencies

Alternative installation files

Download tar.gz 360.77 KB
MD5: 58494d2a98fa53cb088b82bc71ca6772
SHA-1: d391090cc5ac8e870017aefb7e3a392e14738dfa
SHA-256: a8ce7c5fb43b6f0d9e04371934a75ded86903c05ab37c337939beb8ee4aba9df
Download zip 509.6 KB
MD5: a8a912446d0a08e9dce2ee3df02e4b84
SHA-1: ad91121ac380091e17a427b8e516cf70e7ec27a6
SHA-256: fc01082958a19e000626222d32abb82ffc18e03773f61b9423a332687378e6e7

Release notes

Fidelity and safety release. Every preview, risk score, import, export and rollback is now computed from one change set, built the way Drupal core builds an import, and imports and rollbacks are applied by core's configuration importer: what Config Guardian shows is what happens.

1.0.5 could lose configuration or break a site in some cases: a rollback restored fields without their database tables, the Import Configuration form skipped core's validation and the configuration transformations, and a full rollback removed core.extension.yml from the sync directory. Upgrading is strongly recommended.

Upgrading

  • Requires PHP 8.3, as Drupal 11 does, and Drupal ^11.1 || ^12.
  • composer require drupal/config_guardian:^1.1, then run drush updatedb and drush cr before using the module. The update signs the snapshots taken before 1.1.0; a snapshot whose data no longer matches its hash is flagged as corrupt.

Highlights

  • Rollbacks run through core's configuration importer: configuration events, import validators and Config Readonly apply, and fields come back with their tables. The preview lists exactly what the rollback does; configuration created after the snapshot is kept unless you choose to delete it.
  • Snapshots capture every collection, translations included. They are signed, can be pinned, and have a retention policy per type.
  • The Import and Export forms follow core's pipeline and honor Config Split, Config Ignore and $settings['config_exclude_modules'], as Drush does.
  • Risk model 2: an explainable score per change, with core's refusals as blockers. Set risk_model to 1 to keep the 1.0.x score for one minor release.
  • An activity log of every action.
  • Drush 13 and 14. Tested on Drupal 11.1 to 11.4 and on the development versions of 11.5 and 12, with MySQL, PostgreSQL and SQLite.

Changes to review after updating

  • view config snapshots and export config snapshots are now restricted permissions: check which roles hold them.
  • Restoring a snapshot needs restore config snapshots; the Import Snapshot form only stores uploaded files.
  • Risk scores and levels change.
  • Changing the site's hash salt invalidates the signature of every snapshot.

Every change, with the details: CHANGELOG.md.

Created by: andresmoreno28
Created on: 15 Oct 2026 at 15:50 UTC
Last updated: 15 Oct 2026 at 15:51 UTC
Bug fixes
New features

Other releases