Convert to general projects modules that have been released as recipes

Created on 16 August 2024, 7 months ago
Updated 20 August 2024, 7 months ago

Problem/Motivation

Similar to the work done in #3464405: Convert Events recipe-adjacent projects to general projects , I have a number of additional projects that were initially created as modules, but have since been re-released as recipes. These include:

Proposed resolution

Please convert these to general projects, so that composer will correctly ingest their dependency declarations.

📌 Task
Status

Postponed: needs info

Component

Packaging

Created by

🇨🇦Canada mandclu

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

Comments & Activities

  • Issue created by @mandclu
  • Status changed to Postponed: needs info 7 months ago
  • 🇺🇸United States drumm NY, US

    This will move all releases for the project. The releases that were modules will no longer be available from Packages.Drupal.org. I’d like to confirm this is okay before proceeding. We aim to completely minimize disruption to existing sites - even with low usage, we shouldn’t break someone’s build.

    Spot checking the latest module releases of each, I do see "type": "drupal-module", and require in the composer.json files. So these projects are likely not relying on Packages.Drupal.org processing, including dependencies from .info.yml files.

    Are all 4 in a good state for the module versions to be installable when their metadata is on Packagist.org?

Production build 0.71.5 2024