Composer v2: Mark Drupal repository for drupal/* packages only

Created on 4 May 2020, over 4 years ago
Updated 24 July 2024, about 2 months ago

Composer v2 has support to further control how composer repositories should be considered when it determines where to look for packages.

One of the new features is the filtered repositories:

{
    "repositories":[
        {
            "type":"composer",
            "url":"https://packages.drupal.org/8",
            "only": ["drupal/*"]
        }
    ],
}

The "only" configuration makes Composer only lookup drupal/* packages in Drupal repository, which can improve the performance for end users and stop Drupal packagist from receiving requests for other vendor namespaces.

This change is backwards-compatible. Composer v1 users will continue to have same functionality, but v2 users will get the filters affected.

πŸ“Œ Task
Status

Closed: won't fix

Version

11.0 πŸ”₯

Component
BaseΒ  β†’

Last updated 1 minute ago

Created by

πŸ‡±πŸ‡°Sri Lanka Ayesh Everywhere

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.

  • The Needs Review Queue Bot β†’ tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

    Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

    Consult the Drupal Contributor Guide β†’ to find step-by-step guides for working with issues.

  • Status changed to Closed: won't fix about 2 months ago
  • πŸ‡ΊπŸ‡ΈUnited States drumm NY, US

    This can be added, but I would prefer that we did not do this, just in case we do decide to host more namespaces on packages.drupal.org.

    Since this is done server-side, I don’t think there’s a reason for anything in core.

Production build 0.71.5 2024