The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Problem/Motivation
In #3444957: Update current core branches in Drupal 7 Upgrade Status, the Drupal 10 version to check against was bumped from 10.0.x to 10.2.x. In upgrade_status_moved_into_core, the corresponding D10 core version was not updated. Because of this, modules that were previously reported as being moved into Core are no longer reported as such.
Steps to reproduce
Install Drupal 7 core.
Install the entityreference module.
Install upgrade_status module.
Go to `/admin/reports/updates/upgrade` and run the upgrade report against 10.2.x.
Assess that entityreference module is listed as `No compatible release. Yet(?)` instead of indicating it is not part of Drupal Core since 8.x.
Proposed resolution
Update `upgrade_status_moved_into_core` to use 10.2.x instead of 10.0.x for the Drupal 10 review. Something similar was done in #3334584: Update Drupal 7 Upgrade Status for Drupal 9.5's availability.
Remaining tasks
Create MR.
Test.
User interface changes
None.
API changes
None.
Data model changes
None.
Issue fork upgrade_status-3450182
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
compare
Comments
Comment #2
dinarcon commentedAdded a MR with the suggested change.
Comment #5
gábor hojtsyGood find! One line fix makes total sense.
MR had merge conflicts :/ I tried to create another branch to make this easier but that does not want to update from the original repo either without local merge resolution. Strange. Can you help with resolving that or should I directly commit to 7.2.x (with proper attribution of course)?
Comment #8
dinarcon commentedThanks for the quick reply. Committing directly commit to 7.2.x is fine. I am not sure what happened with the issue fork. When I created my PR it was against the
7.x-2.xbranch. I am surprised that it had a merge conflict because my commit changed only one line compared to HEAD. The MR now says that it is against 4.x with a lot more changes. I don't really understand what happened there.BTW, sorry for changing the visibility of the `3450182-projects-moved-into` branch. I was trying to review things and clicked the wrong link. I changed it back to visible.
Comment #10
gábor hojtsyDuh probably I created the MR wrong then. Either way, committed that one line directly, that was easiest, instead of trying to fix the MR. Thanks!