Problem/Motivation
I'm trying to update my project to use drupal/entity_browser_block version 2.0.0, but I'm encountering a dependency conflict with `drupal/entity_browser_block_layout` which is locked at version 1.0.1 and specifically requires drupal/entity_browser_block ^1.0.
This conflict prevents the update and causes the following error during Composer update:
Problem 1
- Root composer.json requires drupal/entity_browser_block ^2.0.0, found drupal/entity_browser_block[dev-2.0.x, 2.0.0, 2.0.x-dev (alias of dev-2.0.x)] but these were not loaded, likely because it conflicts with another require.
Problem 2
- drupal/entity_browser_block_layout is locked to version 1.0.1 and an update of this package was not requested.
- drupal/entity_browser_block_layout 1.0.1 requires drupal/entity_browser_block ^1.0 -> found drupal/entity_browser_block[dev-1.x, 1.0.0-alpha1, ..., 1.x-dev (alias of dev-1.x)] but it conflicts with your root composer.json require (^2.0.0).
Steps to reproduce
- Have a project with drupal/entity_browser_block_layout version 1.0.1 installed
- Try to update to drupal/entity_browser_block version 2.0.0 with the command:
composer update drupal/entity_browser_block:2.0.0 --with-dependencies
- The process fails due to the dependency conflict mentioned above
Proposed resolution
Create a new version of entity_browser_block_layout that is compatible with Drupal 11 and works with drupal/entity_browser_block ^2.0. This would resolve the dependency conflict and enable projects to successfully update to Drupal 11.
Specifically, I propose the following:
- Update the dependency in the module's
composer.json file to support drupal/entity_browser_block ^2.0
- Make necessary code changes to ensure compatibility with Drupal 11's API
- Address any deprecated code or functions that will be removed in Drupal 11
- Ensure all dependencies are also Drupal 11 compatible
This would allow users to smoothly transition their sites to Drupal 11 without having to abandon this module or seek alternatives.
Remaining tasks
User interface changes
No user interface changes are expected.
API changes
Data model changes