>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3343504. --> Reported by: [ambient.impact](https://www.drupal.org/user/1131532) Related to !16 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Super short version: <code>cweagans/composer-patches</code> that we require is breaking DrupalCI and there's no way to add it to the allow list before DrupalCI does the <code>composer install</code>. For details, see <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/config_enforce_devel/-/work_items/3307885" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/config_enforce_devel/-/work_items/3307885</a></span></p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>Run DrupalCI, get Composer require error.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Re-assess which patches we need and whether a new version of a dependency can be required that includes those patches, eventually removing <code>cweagans/composer-patches</code> so that we can run DrupalCI.</p> <h4><a href="https://www.drupal.org/project/multiselect">Multiselect</a> module</h4> <p>We currently require version 8.x-1.2 of this which is the latest of that branch; this doesn't contain the fixes we use patches for; the 2.x branch which (at time of writing) has a beta release does contain the fixes from the patches.</p> <ul> <li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-3"><a href="https://www.drupal.org/project/multiselect/issues/2852660" title="Status: Closed (duplicate)">#2852660: CSS need improvement, causes field following multiselect to wrap</a></span> which is a duplicate of <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/multiselect/issues/2981851" title="Status: Closed (fixed)">#2981851: Floats not cleared</a></span> which is in the beta.</li> <li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/multiselect/issues/3130242" title="Status: Closed (fixed)">#3130242: No schema for multiselect.settings</a></span> is in the beta.</li> </ul> <p>It doesn't look look like either issue is necessary for Config Enforce Devel to function, so we could expand the version constraint to add <code>^2.0</code> and remove the patches, and most or all users will get the newer version with the fixes while technically not breaking backwards compatibility with Drupal 8, which has been end of life for months now.</p> <h4><a href="https://www.drupal.org/project/config_devel">Configuration development</a> module</h4> <p>This one is likely to be the blocker as it doesn't look like the maintainers are present much or at all going back two or three years. Neither of these are even merged, though there is recent activity:</p> <ul> <li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/config_devel/issues/3296836" title="Status: Active">#3296836: Automated Drupal 10 compatibility fixes</a></span> - <del>This is mostly done but some problems with Drupal core version constraints at time of writing. We could go without it, but then we would't be able to support Drupal 10.0 anymore until it's merged.</del> Update: has been merged.</li> <li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-8"><a href="https://www.drupal.org/project/config_devel/issues/3163349" title="Status: Needs review">#3163349: Define hooks to provide 'auto_import' and 'auto_export'</a></span> - This is one is necessary for Config Enforce Devel to function. We should contribute to cleaning up the code in this issue and add some tests for the hooks.</li> </ul> <p>We'll probably have to reach out the maintainers of the module to get these issues looked at once they're ready. We could also ask to be added as maintainers if they don't have time, maybe just temporarily to get these done and released, and then they can remove us as maintainers unless one or more of us have the bandwidth to help out in their issue queue.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>Do the things.</p> <h3 id="summary-ui-changes">User interface changes</h3> <p>Minimal or none, depending on Multiselect.</p> <h3 id="summary-api-changes">API changes</h3> <p>None?</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>None?</p>