Contrib.social

[policy, no patch] composer.phar vs. API (automatic updates)

Open on Drupal.org →
Created on 17 July 2020, almost 5 years ago
Updated 4 September 2024, 10 months ago

Problem/Motivation

This is closely related to #3159972: [policy, no patch] Require Composer 2 for Automatic Updates while still supporting Composer 1 for Drupal 9 generally → . After we have some type of composer v2 available to us, what type of availability should it be? We could embed a version of composer as a phar file. Or we could create a run-time dependency on composer/composer: ^2 that exposes us a PHP API

Proposed resolution

  • The pros to use the PHP API is we have an actual API.
  • The con to using the PHP API are (theoretical) composer dependency issues that get resolved if we contain an embedded phar file.
  • Con to using a phar file is a error out/sys out from calling exec does not make a good API and contains a high risk of being fragile

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

📌 Task
Status

Active

Version

11.0 🔥

Component
Base  →

Last updated about 6 hours ago

Created by

heddn Nicaragua

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024