>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3615577. --> Reported by: [jdleonard](https://www.drupal.org/user/80902) Related to !9 >>> <h3>Problem/Motivation</h3> <p>Since the segment query-access handler landed (#3612937), the base engine hard-depends on <code>drupal/entity</code>, which has no Drupal 12 release. The <code>.info.yml</code> files were narrowed to <code>^11.1</code> and next-major CI was switched off. The documentation was not updated to match, so <code>README.md</code> and <code>CLAUDE.md</code> promise Drupal 12 support the module cannot deliver, and describe CI jobs that no longer run.</p> <p>The same narrowing left a second, quieter problem: the <code>upgrade status</code> job reports readiness for the next major, so with <code>core_version_requirement: ^11.1</code> its only finding is that <code>^11.1</code> is not next-major compatible &mdash; the deliberate state. It has failed on every <code>1.0.x</code> pipeline since, staying invisible because it is <code>allow_failure: true</code>.</p> <p>What the tree actually says today:</p> <pre><pre>entity_segment.info.yml&nbsp;&nbsp;&nbsp; core_version_requirement: '^11.1'<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dependencies: options, user, entity:entity,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; entity_segment:property_traversal, views<br>composer.json&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "drupal/entity": "^1.5"<br>.gitlab-ci.yml&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OPT_IN_TEST_NEXT_MAJOR: 0&nbsp;&nbsp; (no _AUTORUN_NEXT_MAJOR)</pre></pre><h4>Documentation inaccuracies</h4> <ul> <li><strong>README.md</strong> Requirements lists <code>Drupal core ^11.1 || ^12</code>, and claims "Drupal 12 support is available from <code>1.0.0-alpha1</code>. The base engine's own code is verified against Drupal 12 in CI". Neither half holds for <code>1.0.x</code>: the module cannot install on Drupal 12, and no next-major job runs.</li> <li><strong>README.md</strong> <em>Drupal 12 limitations</em> states the pipeline "also runs the next-major (Drupal 12) variant automatically (<code>_AUTORUN_NEXT_MAJOR: 'all'</code>)". That variable is no longer present in <code>.gitlab-ci.yml</code>; the current setting is <code>OPT_IN_TEST_NEXT_MAJOR: 0</code>. The section also attributes the gap to two optional submodules, when the base engine itself is now blocked.</li> <li><strong>README.md</strong> Requirements omits two hard dependencies: <a href="https://www.drupal.org/project/entity">Entity API</a> and the included <code>property_traversal</code> submodule. The module table's dependency column omits <code>views</code> and <code>entity</code>.</li> <li><strong>The three target submodule READMEs</strong> (<code>entity_segment_user</code>, <code>entity_segment_group</code>, <code>entity_segment_crm</code>) each claim <code>^11.1 || ^12</code> while their own <code>.info.yml</code> files declare <code>^11.1</code>, and each claims its code "is Drupal 12 ready, but its test suite cannot be exercised there yet" &mdash; a framing that no longer matches a branch where the base module cannot install on Drupal 12 at all.</li> <li><strong>CLAUDE.md</strong> states "Core support: <code>^11.1 || ^12</code>", and its submodule list omits <code>property_traversal</code>.</li> </ul> <h3>Steps to reproduce</h3> <ol> <li>Read the Requirements section of <code>README.md</code> on <code>1.0.x</code>: it advertises <code>^11.1 || ^12</code>.</li> <li>Read <code>entity_segment.info.yml</code>: <code>core_version_requirement: '^11.1'</code>.</li> <li>Attempt an install on Drupal 12; it fails, because <code>drupal/entity</code> declares <code>^10.1 || ^11</code>.</li> <li>Search <code>.gitlab-ci.yml</code> for <code>_AUTORUN_NEXT_MAJOR</code>, referenced by the README. It is absent.</li> <li>Open any recent <code>1.0.x</code> pipeline and inspect the <code>upgrade status</code> job: it is red under a green pipeline.</li> </ol> <h3>Proposed resolution</h3> <p>Bring the documentation in line with the tree, give the Drupal 12 statement a single source of truth so it does not drift again, and stop the permanently-red job.</p> <ul> <li>Correct the core requirement to <code>^11.1</code> in <code>README.md</code>, <code>CLAUDE.md</code> and the three target submodule READMEs, so every README matches its own <code>.info.yml</code>. Leave <code>property_traversal</code> at <code>^11.1 || ^12</code>, which is correct &mdash; it depends only on core.</li> <li>Add Entity API and the <code>property_traversal</code> submodule to Requirements; add <code>views</code> and <code>entity</code> to the module table's dependency column; add <code>property_traversal</code> to the <code>CLAUDE.md</code> submodule list.</li> <li>Rewrite <em>Drupal 12 limitations</em> to state the current position and point at <code>.gitlab-ci.yml</code> as the authority for the rationale and the exact reversal condition, rather than restating it. Drop the <code>_AUTORUN_NEXT_MAJOR</code> reference. Keep the <code>group</code> and <code>crm</code> notes, reframed as what will still lag once the base blocker clears.</li> <li>Set <code>RUN_JOB_UPGRADE_STATUS: 0</code> alongside the existing next-major opt-out, so both return together when <code>drupal/entity</code> ships a Drupal 12 release.</li> </ul> <h3>Remaining tasks</h3> <ul> <li>Review and merge MR !9.</li> <li>Update the project page description separately &mdash; it is not in the repository and carries the same errors.</li> <li>Plan 11 (<code>drupal-12-support</code>) under <code>.ai/strikethroo/plans/</code> is overtaken by this and may want archiving; its success criteria call for <code>^11.1 || ^12</code> across all five <code>.info.yml</code> files.</li> </ul> <h3>User interface changes</h3> <p>None.</p> <h3>API changes</h3> <p>None. No <code>.info.yml</code> or <code>composer.json</code> constraint changes &mdash; the declared core compatibility is unchanged by this issue.</p> <h3>Data model changes</h3> <p>None.</p>