Why is the recommended release of my module not proposed in Drupal updates? For my contributed module I've previously published several releases without any issue.

Most recent releases were successively 7.x-2.0rc2 then 7.x-2.0 and 7.x-2.1.

As of 7.x-2.1 the following happens:


for all Drupal sites having this module installed with an older release, the admin/reports/updates list doesn't mention the newest release (even after refreshing):

for a site currently in 7.x-2.0rc2 it proposes 7x-2.0
for a site currently in 7.x-2.0 it tells it's up to date

(may be not related but) simultaneously I noticed that the git repository summary doesn't show the labels for the tags corresponding to the 2 new releases, in its Age list


However at the same time:


the project page shows the right last release in Recommended releases (and downloading it gives the right content too)
the git repository summary shows the involved releases in its Tag list


BTW I noticed that some other older releases are also shown in Tag list while missing in Age list, so the git behaviour might not be relevant for this issue

Anynay keep wondering why the recommended release of my module is not proposed in Drupal updates?
Immediately after posting my question, I'd pushed a new 7.x-2.2 release, and it didn't change anything: all involved sites keeped reporting 7.x-2.0 as the most recent release.

But today I noticed that it suddenly changed (without any intervention in git nor in my module's page): now the sites correctly report 7.x-2.2 as the most recent release.

So I tend to think that the response to my question is merely: there is some variable latency in the way Drupal.org makes the information available for the admin/reports/updates/check page underlying mechanism to work.

Moreover it worth mention that also the git Age list now shows all release tags, while some of them were previously missing.