Handle release/project deletion

Open on Drupal.org →

Created on 14 August 2023, over 1 year ago

Updated 2 August 2024, 5 months ago

Occasionally releases are deleted, leaving composer namespace debris. We can delete:

From project_composer_component when a release is deleted
From project_composer_namespace_map when a project is deleted
Remove or regenerate files/packages/8/p2/drupal/[project]~dev.json
Remove or regenerate files/packages/8/p2/drupal/[project].json

📌 Task

Status

Active

Version

1.0

Component

Code

Created by

🇺🇸United States drumm NY, US

Live updates comments and jobs are added and updated live.

Sign in to follow issues

Comments & Activities

Issue created by @drumm
Comment over 1 year ago →
🇺🇸United States drumm NY, US
Comment about 1 year ago →
🇺🇸United States drumm NY, US
Comment 5 months ago →
🇺🇸United States drumm NY, US
We also could use a way to clean up metadata that we no longer want to host, for cases like #3464405: Convert Events recipe-adjacent projects to general projects →

Comment 5 months ago →

drumm → committed 4921476c on 7.x-1.x

Issue #3381080: Add DB column to track deletions, refactor filename...

Comment 5 months ago →
System Message

drumm → committed 0d88f69d on 7.x-1.x
Issue #3381080: Rename to avoid reserved word
Comment 5 months ago →
System Message

drumm → committed 1070e120 on 7.x-1.x
Issue #3381080: Add drush command to delete a project’s metadata
Comment 5 months ago →
System Message

drumm → committed e4cc39c6 on 7.x-1.x
Issue #3381080: Fix missing argument
Comment 5 months ago →
🇺🇸United States drumm NY, US
This drush command likely needs updating to get all of the component metadata json files cleared out.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024