When attempting to merge the cu_base changes in the root, upstream composer.json with the root, project composer.json, we are getting merge conflicts even after the initial merge conflict was resolved. This is because of a style difference in the additional level Webform adds to the custom repos.
The result of the merge requires manually fixes. By simply added a name like "drupal/taxonomy_revision_ui": and "cu-uis/cu_base" to the custom packages we've added at the upstream level, we'd stop having these conflicts with Autopliot and drush webform:composer:update
Describe the bug
When attempting to merge the cu_base changes in the root, upstream composer.json with the root, project composer.json, we are getting merge conflicts even after the initial merge conflict was resolved. This is because of a style difference in the additional level Webform adds to the custom repos.
It's the "tippyjs/6.x": that is different than the entries that start with just { "type":
The result of the merge requires manually fixes. By simply added a name like "drupal/taxonomy_revision_ui": and "cu-uis/cu_base" to the custom packages we've added at the upstream level, we'd stop having these conflicts with Autopliot and
drush webform:composer:update