From 8bc708274d90879546b15a4edb0e9da7d4b59eb4 Mon Sep 17 00:00:00 2001 From: Alex Skrypnyk Date: Tue, 17 Nov 2026 09:16:32 +1100 Subject: [PATCH 1/7] [#3311] Added a 7-day Composer 'cooldown' policy with Drupal core exempt. --- composer.json | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/composer.json b/composer.json index 6be96e98a3..f961a4d071 100644 --- a/composer.json +++ b/composer.json @@ -120,6 +120,13 @@ }, "abandoned": { "audit": "report" + }, + "cooldown": { + "period": "7 days", + "ignore": { + "drupal/core": "Drupal core security releases need to be applied immediately.", + "drupal/core-*": "Drupal core security releases need to be applied immediately." + } } }, "sort-packages": true From ab474533c80cca11447a0eafc1c13b93ec0f5634 Mon Sep 17 00:00:00 2001 From: Alex Skrypnyk Date: Tue, 17 Nov 2026 09:18:08 +1100 Subject: [PATCH 2/7] [#3311] Documented the Composer release cooldown and the '--no-cooldown' path for urgent security releases. --- .vortex/docs/content/development/composer.mdx | 55 ++++++++++++++++++- .../development/dependency-updates.mdx | 10 ++++ .../development/security/dependency-audit.mdx | 3 +- 3 files changed, 66 insertions(+), 2 deletions(-) diff --git a/.vortex/docs/content/development/composer.mdx b/.vortex/docs/content/development/composer.mdx index 5603e85c79..749da04567 100644 --- a/.vortex/docs/content/development/composer.mdx +++ b/.vortex/docs/content/development/composer.mdx @@ -208,6 +208,57 @@ closely at the scaffold files that core updates, such as `web/index.php` and overwrites it. When a core release changes `.htaccess`, port the change by hand. +### Release cooldown + +`composer update` and `composer require` skip any package version published +less than 7 days ago. A compromised release is often detected and pulled +within days, so the delay keeps it out of your project. `composer install` +installs what `composer.lock` pins, so the cooldown doesn't affect it. + +**Vortex** sets the delay in the `cooldown` section of +[`config.policy`](https://getcomposer.org/doc/06-config.md#policy): + +```json +"cooldown": { + "period": "7 days", + "ignore": { + "drupal/core": "Drupal core security releases need to be applied immediately.", + "drupal/core-*": "Drupal core security releases need to be applied immediately." + } +} +``` + +The `ignore` entries exempt the Drupal core packages, so a core security +release installs on the day it's published. `drupal/core-recommended` pins +exact versions of the packages core depends on, such as Symfony. The +cooldown still holds back a pinned version younger than 7 days. Composer +then resolves the older core release, or fails when your constraint needs +the new one. It reports the versions it holds back: + +```text +3 package version(s) withheld by the cooldown policy (run with -vv to list them). +``` + +To install a release before it's 7 days old, such as an urgent security +fix, add `--no-cooldown` to the update command: + + + + ```shell + ahoy composer update "drupal/core-*" --with-dependencies --no-cooldown + ``` + + + ```shell + docker compose exec cli composer update "drupal/core-*" \ + --with-dependencies --no-cooldown + ``` + + + +To change the delay, edit `period`, such as `"3 days"`. Set it to `null` to +turn the cooldown off. The cooldown requires Composer 2.11 or later. + ### Dependency bumping [Dependency bumping](https://getcomposer.org/doc/03-cli.md#bump) raises the @@ -751,7 +802,9 @@ following keys: vulnerabilities stay visible without breaking reproducible builds. Abandoned packages show up in the report without failing it. ➡️ See [Dependency audit](security/dependency-audit.mdx) for the option values, - how to ignore advisories and the CI integration. + how to ignore advisories and the CI integration. The `cooldown` section + holds back releases younger than 7 days, except Drupal core. ➡️ See + [Release cooldown](#release-cooldown). - [`bump-after-update`][bump-after-update]: Runs `composer bump` after every `composer update`, which raises the version constraints in `composer.json` to the installed versions. diff --git a/.vortex/docs/content/development/dependency-updates.mdx b/.vortex/docs/content/development/dependency-updates.mdx index 1ec220f8df..9345bf415d 100644 --- a/.vortex/docs/content/development/dependency-updates.mdx +++ b/.vortex/docs/content/development/dependency-updates.mdx @@ -127,6 +127,9 @@ after. Drupal core has no delay, so a core security release is proposed on the next daily run. Its rule in `renovate.json` carries a `description` that says so. +Composer's [release cooldown](composer.mdx#release-cooldown) exempts the +core packages too. Renovate's update of `composer.lock` then fails only +when the release pins a dependency younger than 7 days. #### Registries without release dates @@ -170,6 +173,13 @@ after it reads the advisory. The PR skips the minimum release age, the group's schedule and the limit on open PRs. It updates the affected dependency to the lowest release that fixes the advisory. +Composer's [release cooldown](composer.mdx#release-cooldown) still applies +when Renovate updates `composer.lock`. When the fix, or a dependency it +pins, is younger than 7 days, the lock update fails. Renovate then reports +an artifact update problem on the PR. To apply the fix, check out the PR +branch, run `ahoy composer update` for the package with `--no-cooldown` +and push the result. + Advisory PRs carry the `Dependencies` and `Security` labels, so they stand apart from routine updates. The `vulnerabilityAlerts` setting in `renovate.json` sets the labels: diff --git a/.vortex/docs/content/development/security/dependency-audit.mdx b/.vortex/docs/content/development/security/dependency-audit.mdx index d163e90d4e..41907ac53e 100644 --- a/.vortex/docs/content/development/security/dependency-audit.mdx +++ b/.vortex/docs/content/development/security/dependency-audit.mdx @@ -124,7 +124,8 @@ rest, including the `malware` and `cooldown` policies and the per-entry :::note Composer 2.10+ `config.policy` requires Composer 2.10 or newer, which ships in the -**Vortex** container images. On older Composer versions, use the legacy +**Vortex** container images. The `cooldown` section requires Composer 2.11 +or newer. On older Composer versions, use the legacy `config.audit` keys (`block-insecure`, `abandoned`) instead. Composer 2.10 and newer still read those keys, but only when the matching `config.policy` section is absent. From 96759948a925fe3cb5dceeb323ad4115bc23472c Mon Sep 17 00:00:00 2001 From: Alex Skrypnyk Date: Tue, 17 Nov 2026 09:18:28 +1100 Subject: [PATCH 3/7] Updated snapshots. --- .../tests/Fixtures/handler_process/_baseline/composer.json | 7 +++++++ .../Fixtures/handler_process/hosting_acquia/composer.json | 2 +- .../hosting_project_name___acquia/composer.json | 2 +- .../starter_drupal_cms_profile/composer.json | 2 +- 4 files changed, 10 insertions(+), 3 deletions(-) diff --git a/.vortex/installer/tests/Fixtures/handler_process/_baseline/composer.json b/.vortex/installer/tests/Fixtures/handler_process/_baseline/composer.json index 9639a7ee18..cd5f018aca 100644 --- a/.vortex/installer/tests/Fixtures/handler_process/_baseline/composer.json +++ b/.vortex/installer/tests/Fixtures/handler_process/_baseline/composer.json @@ -108,6 +108,13 @@ }, "abandoned": { "audit": "report" + }, + "cooldown": { + "period": "7 days", + "ignore": { + "drupal/core": "Drupal core security releases need to be applied immediately.", + "drupal/core-*": "Drupal core security releases need to be applied immediately." + } } }, "sort-packages": true diff --git a/.vortex/installer/tests/Fixtures/handler_process/hosting_acquia/composer.json b/.vortex/installer/tests/Fixtures/handler_process/hosting_acquia/composer.json index 3018aaa8a7..fcac2e6a0c 100644 --- a/.vortex/installer/tests/Fixtures/handler_process/hosting_acquia/composer.json +++ b/.vortex/installer/tests/Fixtures/handler_process/hosting_acquia/composer.json @@ -1,4 +1,4 @@ -@@ -131,38 +131,38 @@ +@@ -138,38 +138,38 @@ "[web-root]/update.php": false }, "locations": { diff --git a/.vortex/installer/tests/Fixtures/handler_process/hosting_project_name___acquia/composer.json b/.vortex/installer/tests/Fixtures/handler_process/hosting_project_name___acquia/composer.json index 3018aaa8a7..fcac2e6a0c 100644 --- a/.vortex/installer/tests/Fixtures/handler_process/hosting_project_name___acquia/composer.json +++ b/.vortex/installer/tests/Fixtures/handler_process/hosting_project_name___acquia/composer.json @@ -1,4 +1,4 @@ -@@ -131,38 +131,38 @@ +@@ -138,38 +138,38 @@ "[web-root]/update.php": false }, "locations": { diff --git a/.vortex/installer/tests/Fixtures/handler_process/starter_drupal_cms_profile/composer.json b/.vortex/installer/tests/Fixtures/handler_process/starter_drupal_cms_profile/composer.json index c2c7f460f6..25df4246c3 100644 --- a/.vortex/installer/tests/Fixtures/handler_process/starter_drupal_cms_profile/composer.json +++ b/.vortex/installer/tests/Fixtures/handler_process/starter_drupal_cms_profile/composer.json @@ -39,7 +39,7 @@ }, "bump-after-update": true, "discard-changes": true, -@@ -169,6 +176,17 @@ +@@ -176,6 +183,17 @@ "patchLevel": { "drupal/core": "-p2" }, From b1f858270cb0e5ab653a551402485c03046d0bcb Mon Sep 17 00:00:00 2001 From: Alex Skrypnyk Date: Tue, 17 Nov 2026 09:24:49 +1100 Subject: [PATCH 4/7] [#3311] Documented that a full update within the cooldown can move indirect dependencies back. --- .vortex/docs/content/development/composer.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.vortex/docs/content/development/composer.mdx b/.vortex/docs/content/development/composer.mdx index 749da04567..604521f861 100644 --- a/.vortex/docs/content/development/composer.mdx +++ b/.vortex/docs/content/development/composer.mdx @@ -256,6 +256,12 @@ fix, add `--no-cooldown` to the update command: +The cooldown applies again on your next full `composer update`. For 7 days, +that update can move an indirect dependency from the new release back to +an older one. [Dependency bumping](#dependency-bumping) raises the +constraint of each package you require directly, so those stay on the new +release. Add `--no-cooldown` to each full update in that window. + To change the delay, edit `period`, such as `"3 days"`. Set it to `null` to turn the cooldown off. The cooldown requires Composer 2.11 or later. From 54e57085294c49c10d0dbfe86724e8cd40690c48 Mon Sep 17 00:00:00 2001 From: Alex Skrypnyk Date: Tue, 17 Nov 2026 09:25:00 +1100 Subject: [PATCH 5/7] [#3311] Scoped the cooldown docs to tagged releases and to installs from a lock file. --- .vortex/docs/content/development/composer.mdx | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/.vortex/docs/content/development/composer.mdx b/.vortex/docs/content/development/composer.mdx index 604521f861..3d43786d00 100644 --- a/.vortex/docs/content/development/composer.mdx +++ b/.vortex/docs/content/development/composer.mdx @@ -210,10 +210,12 @@ hand. ### Release cooldown -`composer update` and `composer require` skip any package version published +`composer update` and `composer require` skip any tagged release published less than 7 days ago. A compromised release is often detected and pulled -within days, so the delay keeps it out of your project. `composer install` -installs what `composer.lock` pins, so the cooldown doesn't affect it. +within days, so the delay keeps it out of your project. Branch versions +such as `dev-main` change with every commit, so the cooldown leaves them +alone. With a `composer.lock`, `composer install` installs what the lock +pins, so the cooldown doesn't affect it. **Vortex** sets the delay in the `cooldown` section of [`config.policy`](https://getcomposer.org/doc/06-config.md#policy): From 535a08b7825a04c7e847cee19ce5b587ee9ab0bf Mon Sep 17 00:00:00 2001 From: Alex Skrypnyk Date: Tue, 17 Nov 2026 09:25:06 +1100 Subject: [PATCH 6/7] [#3311] Added '--with-dependencies' to the security fix update with '--no-cooldown'. --- .vortex/docs/content/development/dependency-updates.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.vortex/docs/content/development/dependency-updates.mdx b/.vortex/docs/content/development/dependency-updates.mdx index 9345bf415d..e77aff2c34 100644 --- a/.vortex/docs/content/development/dependency-updates.mdx +++ b/.vortex/docs/content/development/dependency-updates.mdx @@ -177,8 +177,8 @@ Composer's [release cooldown](composer.mdx#release-cooldown) still applies when Renovate updates `composer.lock`. When the fix, or a dependency it pins, is younger than 7 days, the lock update fails. Renovate then reports an artifact update problem on the PR. To apply the fix, check out the PR -branch, run `ahoy composer update` for the package with `--no-cooldown` -and push the result. +branch, run `ahoy composer update` for the package with +`--with-dependencies --no-cooldown` and push the result. Advisory PRs carry the `Dependencies` and `Security` labels, so they stand apart from routine updates. The `vulnerabilityAlerts` setting in From 66d7a9ee3b3c78fa3bb2c5b16ab96cdc0901be08 Mon Sep 17 00:00:00 2001 From: Alex Skrypnyk Date: Tue, 17 Nov 2026 09:25:18 +1100 Subject: [PATCH 7/7] [#3311] Clarified which releases a full update within the cooldown moves back. --- .vortex/docs/content/development/composer.mdx | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/.vortex/docs/content/development/composer.mdx b/.vortex/docs/content/development/composer.mdx index 3d43786d00..16134249c3 100644 --- a/.vortex/docs/content/development/composer.mdx +++ b/.vortex/docs/content/development/composer.mdx @@ -258,11 +258,12 @@ fix, add `--no-cooldown` to the update command: -The cooldown applies again on your next full `composer update`. For 7 days, -that update can move an indirect dependency from the new release back to -an older one. [Dependency bumping](#dependency-bumping) raises the -constraint of each package you require directly, so those stay on the new -release. Add `--no-cooldown` to each full update in that window. +The cooldown applies again on your next full `composer update`. Until the +releases you installed are 7 days old, that update can move an indirect +dependency back to an older release. [Dependency +bumping](#dependency-bumping) raises the constraint of each package you +require directly, so those packages keep the release you installed. Add +`--no-cooldown` to each full update until then. To change the delay, edit `period`, such as `"3 days"`. Set it to `null` to turn the cooldown off. The cooldown requires Composer 2.11 or later.