file_mdm 3.2.0 update notification issues

I am assuming this the same issue as File metadata manager being listed on my updates page as not compatible and recommending we move to 3.2.0 even though we are still on Drupal 10.4.6 (moving to 10.5.1 soon but not 11 yet). We don't have emails set up so it isn't as bothersome but I did want to point it out as a bit confusing.

The Drupal Core Update module is basically using the major release number to determine what should be allowed to be installed. The function update_calculate_project_update_status throws away information because it does not account for core compatibility. The setReleaseMessage function inserts the compatibility information ... but too late.

Anyway, here is what I did so I can continue to get valid email about updates. Rather than patch Core, here is a workaround that forces the recommended version. Create a module with the following function inside the module file. Use with caution, since you need to verify that is the latest compatible release.

function club_update_projects_alter(&$projects): void {
  if (isset($projects['file_mdm'])) {
    $projects['file_mdm']['recommended'] = '3.1.0';
  }
}

The best fix would be for @mondrake to make a new release 4.x.x for Drupal 11, and 3.2.1 for Drupal 10.