>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3074998. --> Reported by: [tedbow](https://www.drupal.org/user/240860) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Once <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2313917" title="Status: Closed (fixed)">#2313917: Core version key in module's .info.yml doesn't respect core semantic versioning</a></span> is committed then the same module/theme will able to be compatible with multiple version of Drupal core</p> <p>I created <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/3074993" title="Status: Closed (fixed)">#3074993: Use "current" in update URLs instead of CORE_COMPATIBILITY to retrieve all future updates</a></span> so that the update module can get all project updates for project.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>After #2313917 the new 'core_dependency'(if used) could be return for each project so the Drupal Update module could determine if each release is compatible.</p> <p>Either that or the update server could filter which modules are compatible with the current version of Drupal core.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>Figure out the solution</p> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <p>Some new info will be provide or module releases will be pre-filtered.</p> <h3 id="summary-data-model-changes">Data model changes</h3> <h3 id="summary-release-notes">Release notes snippet</h3> > Related issue: [Issue #2188661](https://www.drupal.org/node/2188661) > Related issue: [Issue #2313917](https://www.drupal.org/node/2313917) > Related issue: [Issue #3076183](https://www.drupal.org/node/3076183)