Temporarily remove Ultimate Cron until it has a stable release, to resolve on Stable for Drupal CMS

Rajab Natshahrequested to merge
issue/varbase_performance_base-3621493:3621493-temporarily-remove-ultimate into 1.0.x

Issue: #3621493

drupal/ultimate_cron has no stable release, so a project on Composer's default minimum-stability: stable cannot install this recipe. All four Varbase site templates apply it directly, so it blocks every one of them on Drupal CMS.

Temporary. Ultimate Cron goes back when it has a stable release. Requested in #2660208.

An existing Varbase site keeps it: vardot/varbase requires it in the profile since #3621480.

What changed

  • composer.json: dropped drupal/ultimate_cron.
  • recipe.yml: dropped ultimate_cron from the install: list.
  • Removed the sixteen config/ultimate_cron.job.*.yml files. A recipe imports everything in config/, so leaving them would fail the apply once the module is gone. The directory is now empty and dropped.

A new site falls back to core's Automated Cron, which this recipe already sets to automated_cron.settings.interval: 10800. What it loses is per-job scheduling, per-job logging and the cron overview screen.

Checkpoints

  • Addition/Change/Update/Fix
  • Testing to ensure no regression
  • Reviewed by a human
  • Code review by maintainers
  • Release

This work was done with the help of AI, and reviewed by a human. Per the Drupal AI policy.

Edited by Rajab Natshah

Merge request reports