Drush pm-update: How can I stop it from trying to update more recent dev releases? I'm using drush 5 to update the modules on my site.  Usually it works great.  However, when I have downloaded a dev release, even if there is no more recent point release it tries to update the dev release module to the last official "point" release.

For example, I have heartbeat-dev installed (2012-Mar-20).  Yet when I run the drush up command, it prompts me to update to heartbeat 1.0 (2011-Jun-25).

If there is a newer dev release, I want to update to that.  If there is a newer point release, I want to update to that.  But if I have a dev release and the point release is older, I don't want to update.  How can I do this?

I've been handling this manually but as the number of modules on my site grows it's getting harder to keep track of which to update and which not to update...
Basically, this sounds like a bug that should be addressed in the drush issue queue.  I'm guessing this is recent; it used to be that Drush would never go from dev to stable unless you used pm-download.  Now it is being a bit overzealous.

As a workaround, you can use the --lock option to stop Drush from updating the module at all (drush pm-update --lock=heartbeat), but this will also exclude newer dev releases as well.