Contrib.social

Installer cache priming should only happen for tagged releases

Open on Drupal.org →
Created on 16 December 2024, 6 days ago

Problem/Motivation

The pre-warmed recipe cache is currently added to the installer on every commit. This introduces a risk of breaking the installer if the installer cache is generated from the dev head, but Composer installs tagged versions of the relevant recipes (which it is inclined to do, as prefer-stable: true is set in the project template's composer.json).

Proposed resolution

Only do the cache priming for tagged releases. If you get a dev snapshot of Drupal CMS, the installer will be a bit slower since it needs to parse the recipes from scratch, but that's an acceptable trade-off because we don't expect most people to use our dev snapshots. And besides, recipe parsing is faster than it used to be thanks to the addition of a static caching layer in core.

🐛 Bug report
Status

Active

Component

Track: Installer

Created by

🇺🇸United States phenaproxima Massachusetts

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024