Drush downloading wrong module version patch

By default, drush pm-update will update Drupal core and all enabled projects to the latest recommended releases. The optional project argument allows you to provide a list of installed projects to update, thereby limiting the scope of the update. You can also pass a specific version of Drupal core as a project argument and Drush will limit the upgrade to that version of core and core only, unless you pass other projects along as arguments. Sign up to join this community.

The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. How can I update a module to a specific version using Drush? Ask Question. Asked 3 years, 4 months ago. Active 8 months ago. Viewed 6k times. I am trying to update module entityform 7.

Can we update module at specific version using drush? Improve this question. Add a comment. Active Oldest Votes. Improve this answer. Pankaj Yogi Pankaj Yogi 1 1 gold badge 11 11 silver badges 22 22 bronze badges. Sign up or log in Sign up using Google. You apply the patch, it fixes the bug and all is well with the world.

That is until it comes time to update this contrib module. Maybe a different developer is performing the update, or maybe it is just you months years? You don't necessarily remember that you previously patched this specific module and when you update it, you unintentionally overwrite the patched fix, reintroducing the bug. To lessen the chances of this occurring, we want to be able to track all of the patches that have been applied, and ensure that they are re-applied every time the underlying code has been updated.

In the past, we manually tracked patches in a directory at the top level of our git repository. Within this 'patches' directory, we have a folder for Drupal core patches and a folder for each contrib module that has had a patch applied. When a module is updated, it is up to the developer to consult this directory structure and identify any patches that may need to be reapplied. While this is technically a viable system, it is easy to see that there is at least one major flaw. It is not uncommon for a developer to simply forget to check the patches directory.

Recently, we have begun to utilize Drush Patch File to improve this workflow. Drush Patch File endeavors to simply document and track what patches have been applied, and automatically reapply patches when a module has been updated.

With Drush Patch File, our legacy 'patches' folder still exists, but we replace its contents with a patches. Point drush to your patches.