The Netlobo logo - a Nevada desert landscape

Drupal Module Recommended Release Drush Error

This article gives a solution to the drush error message: There is no *recommended* release for project X

Published Jan 26, 2011 by lobo235
Last updated on Jul 5, 2011

I use Drush to download my new modules for the Drupal sites I build. There have been multiple instances when I have encountered a Drush error message that states "There is no *recommended* release for project X" when I try to download a new module. This can sometimes be frustrating because it means that you either need to download the module manually or you need to specify the specific version of the module you want to download. Module maintainers can easily fix this Drush message for users who use Drush to download the module by marking a specific version of their module as the "Recommended" version.

If you are encountering this error message just go to the issue queue for the Drupal module you are trying to download and put a task in the issue queue for the module maintainer(s) to specify a "Recommended" release. The maintainers will then be able to edit the recommended release setting by editing the module's project page on If you are a module maintainer who is trying to resolve this drush error for your users please see the following steps.

How to Set a Recommended Release as a Drupal Module Maintainer

  • Login to
  • Visit your module's project page
  • Click the edit link to edit the project page
  • Click on the "Releases" tab
  • You will now see a page that looks like the screenshot on the right
  • Make sure you select a major version in the select box labeled "Recommended major version"
  • Save the form

Still Not Working?

If you are still having problems with the Drush error about not having a recommended release then you may need to simply add another release if you only have one. The easiest thing to do is to create a dev release. After creating a dev release for your module and setting the Recommended major version you shouldn't have problems with this anymore.

If you were able to resolve this issue using a different method or if you have any additional insight into the root cause of this problem then please leave a comment so that you can help others out with this problem.

This is a test!

0 comments for this article. Be the first to leave one!