As of
📌
Clean up problematic 2.x branch
Active
, IEF development continues in 3.x branch.
People can only upgrade if all their projects require drupal/inline_entity_form ^1 || ^3
Whoever gets stuck on sth like this, please open an issue in the respective project, and set this issue as parent.
How to find out which projects block IEF 3:
composer why-not drupal/inline_entity_form ^3
Subject: Require IEF ^1 || ^3
Problem/Motivation
For reasons, the inline_entity_form module has to continue development on a 3.x branch, with no disruption from 1.x.
Projects requiring IEF should, for a smooth transition, allow both versions as requirement.
Example composer.json fragment:
"require":
"drupal/inline_entity_form": "^1.0@rc || ^3.0.0@rc",
Proposed resolution
Update the requirement.
Active
3.0
Code
I think it maybe helpful to show more quicly show people what the 'new work' on v3 now is then to understand if they need to stay on V1 (if they use other contrib that also still specifies v1) and that the new work is more normal contrib progression.
As IFE seems to want to be able to get a GM release -- and just move forward into v3.
