Problem/Motivation

In #3540215: Remove the ability to configure the path to Composer, we removed support for the package_manager.settings:executables config structure. But we did not remove the config values themselves, because we don't want to break sites relying on them.

As detailed in #3540215-20: Remove the ability to configure the path to Composer, the idea is that we will remove them as part of the upgrade path to Drupal 12. In this issue, let's create that upgrade path. At the moment, I'm filing this against 11.x because 12.x isn't branched yet.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Comments

phenaproxima created an issue. See original summary.

phenaproxima’s picture

Status: Active » Postponed
catch’s picture

Issue tags: +Drupal 12 upgrade path
quietone’s picture

Issue summary: View changes
Issue tags: -Drupal 12 upgrade path +Upgrade path, +12.0.0 release priority

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.