- Issue created by @ericvl
- 🇳🇱Netherlands dhendriks
Indeed, stuck with Drupal 10.2.7 and file_mdm 3.0.0 (latest Drupal core with latest file_mdm that works with it). Getting update notifications multiple times per day. A bit annoying. Drupal 10.3 is released tomorrow, so hopefully I can upgrade both to resolve this situation.
- 🇮🇹Italy mondrake 🇮🇹
Not something that can be solved by the module itself, which is setting its own constraints.
This is another problem with the core update - which is not taking care of checking if newer versions of modules are compatible with current core, AFAICS
- 🇧🇪Belgium ericvl
This issue is indeed not the fault of this module, you're right.
So, this issue can be closed by a maintainer.Thank you for the clear explanation.
Greetings. - 🇮🇹Italy mondrake 🇮🇹
Moving to Drupal core issue queue this as well, like the referenced one.
Some more explanation for core:
It looks like this happens if you release a full version of a contrib module that has as minumum core requirement a version of that is not released yet.
In this case, File Metadata Manager 3.1.0 was released on June 11, 2024, with a core constraint = "^10.3 | ^11". Since neither 10.3 nor 11 have a full release yet, we incur in the OP.