I recently got into a bind as a result of our automatic build scripts not producing the same results on differnet environments. Turns out it was related to drush's caching of the release xml files. By default, drush make caches the release xml for a module for 1 day

The logic currently works this way:
type drush make
drush uses cached release xml files if it has it
if it finds that the user requested a version that it does not have, it prints a warning and uses an older verison

i think it should work like this
1) drush uses cached release xml file if it has it
2) if it finds that the user is requesting a NEWER version that the newest version that it knows about in its current xml file, try to re-download the release xml file to see if there has been a recent release it doesn't know about

Alternatively, it should fail if it can't find the module version you are looking for. (Is there a setting for this?)

Comments

moshe weitzman’s picture

Version: » 8.x-6.x-dev
Assigned: Unassigned » jonhattan

Seems reasonable. Not sure if it will be clean to implement. Assigning to jonhattan.

greg.1.anderson’s picture

Status: Active » Closed (won't fix)
Issue tags: +Needs migration

This issue was marked closed (won't fix) because Drush has moved to Github.

If this feature is still desired, you may copy it to our Github project. For best results, create a Pull Request that has been updated for the master branch. Post a link here to the PR, and please also change the status of this issue to closed (duplicate).

Please ask support questions on Drupal Answers.