Even though I have all these modules installed, Release Monitor is telling me to upgrade to the exact same version:
-cck_field_perms 5.x-1.4
-date 5.x-1.2
-daterange 5.x-1.2
-freelinking 5.x-1.1
-token 5.x-1.4

Is there is indeed a minor revision (e.g., 1.4.0 to 1.4.1), Release Monitor needs to tell me this.

Comments

aren cambre’s picture

aren cambre commented

Just for giggles, I downloaded and installed the versions that the download button gave me, but it still says that newer versions of those modules are available even after requerying at /admin/settings/releasemonitor.

Yes, I did a ctrl-refresh on /admin/build/releases just to be for sure.

I also went through /update.php even though it said no updates were needed.

Release Monitor did notice that new copies of the products were installed; it pointed that out before I made it requery.

douggreen’s picture

douggreen commented
Status: Active » Closed (won't fix)

This version of Release Monitor looks at CVS ids and tags. If you look at the CVS ids for these modules on your system (the $Id$ value at the top of the .module files), then browse the module in CVS, I suspect that you'll see that there are minor updates available, only that the developer hasn't put them into a tagged release yet.

I hope to make improvments to this end ready for Drupal 6, but in Drupal 5, that's not how this module works works. I'd like to add a third column, major updates (i.e., your on D5 and a D6 tag is ready), minor updates (i.e., your on 5.x-1.1 and 5.x-1.2 is ready), and developer updates (a new CVS version is available, but not yet tag for release). Right now, minor updates are really developer updates.