>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #2948861. --> Reported by: [Mixologic](https://www.drupal.org/user/391689) >>> <p>When a module has a dependency on another module in a project that isnt the primary, name matching module, it introduces a dependency in composer.json that locks the submodule on a version, which then requires the owners to upgrade all locked submodules as well as the parent project at the same time in order to upgrade the parent project.</p> <p>This is a result of the submodules' metapackage data having a require on 'self.version' of the parent project. If we change this to '*' it will be much more relaxed, but it *may* mean that modules cannot use version constraints to rely on the other modules, causing the wrong version to be installed.</p> <p>We'll need to experiment with various use cases to make sure this can work.</p> > Related issue: [Issue #2998609](https://www.drupal.org/node/2998609)