I got this for a while, and it came down to the method I'd used to do the update.
I'd merged the changes onto my site, but turns out I'd merged from a point release (bundled TGZ) to an update version (git tagged).
All the code was updated, *but* the version numbers in the .info files were stuck at the old number.
This put the update report into a bit of confusion - like your picture shows.
I eventually traced it by looking ad (eg) modules/block/block.info and seeing the version number there was outdated.
This may not be the same issue for you, but it reminds me of what happened to me.
Comments
It probably just hasn't
It probably just hasn't communicated with the external server to realize that it is at the current version.
Contact me to contract me for D7 -> D10/11 migrations.
I still get a lot of errors
I still get a lot of errors though :O
Even though they dont affect the sites looks.
Also it's been a weekish and Drupal still says there's an update O_O
You're not the only one. I
You're not the only one. I think that these things happen from time to time.
I got this for a while, and
I got this for a while, and it came down to the method I'd used to do the update.
I'd merged the changes onto my site, but turns out I'd merged from a point release (bundled TGZ) to an update version (git tagged).
All the code was updated, *but* the version numbers in the .info files were stuck at the old number.
This put the update report into a bit of confusion - like your picture shows.
I eventually traced it by looking ad (eg) modules/block/block.info and seeing the version number there was outdated.
This may not be the same issue for you, but it reminds me of what happened to me.
.dan. is the New Zealand Drupal Developer working on Government Web Standards