Out of date

I would have to assume you have been using v4.0.3 through your entire Drupal 10 life cycle?

I'm also seeing this issue. Everything is correctly reported as up-to-date when using Composer but on your Drupal site go to:

[yoursite.com]/admin/reports/updates and it says there's an update available for Dropdown_Language from version 4.0.3 to 4.1.0 but also lists it as incompatible, since it is not compatible with Drupal 10.

We would expect it to show that no update is available since it's not compatible with our version of Drupal. It also means that if you've got Email Notifications set up you get daily emails stating updates are available when there's not.

I hope this information helps you find a solution to this issue. I have also attached a screenshot of the issue.

core_version_requirement is correctly set by {dropdown language} for both these releases, and follows my long-term tagging strategy. as does my composer setup to keep major core version apart with my release cycles.

-> I have no control over Update Manager messaging. this bug seems like theres, not mine.

otherwise, Dropdown Language is operating normally correct? (:

again, i blame update manager: this is confusing that the 4.1 line is indeed not with 10.3 (as it was in 10.2). i can not guess at the 'Requires Drupal core:" is blank off hand. again, this is internal to update manager.

low concern.

same here... This message keeps the drupal installation in an outdated state.

The Linkit module had a similar problem, that we could patch it like 💬 Update module erroneously recommends conflicting update to 6.1.x for sites on Drupal 10.0.x or lower Closed: works as designed

💬 Update module erroneously recommends conflicting update to 6.1.x for sites on Drupal 10.0.x or lower Closed: works as designed is using an update hook of Update Module to 'short-cut' this.

if the problem is still (untill d11 is actually out, and if core themselves need to update Update module around this in a wider way across conbrib -- i will continue to wait to see that result.

We are on Drupal 11.0.5 and yet this message still marks the Drupal 10.3 as Outdated

If we have 4.0.3 that is still supported, on Drupal 10.3, the installation should not be marked as outdated.

this is how this module is currently set for release status:

it seems like core isn't figuring out that what's recommended isn't geared per core release.

certainly, lots of open tickets around this in core..

Drupal issues search | "text=not+compatible&component=update.module" →