Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Drush make currently just rewrites the version in the .info file to be the git hash in the event of a git clone from a hash. Drupal.org rewrites using more ineligible logic (eg, 5 commits past last stable, etc) so as to not cause panic when somebody views the available updates screen from within Drupal. The code d.o. uses is here: http://drupalcode.org/project/drupalorg.git/blob/refs/heads/6.x-3.x:/dru...
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | drush-make-info-rewrite-1693452-03.patch | 2.47 KB | jhedstrom |
| #1 | drush-make-info-rewrite-1693452-01.patch | 897 bytes | jhedstrom |
Comments
Comment #1
jhedstromTurns out this was actually a regression. Tagging the .git directory for removal after the build instead of removing it at the time of download allows the logic found in
drush_pm_git_drupalorg_compute_rebuild_version()to work properly again.Setting to needs review for now, but will commit shortly.
Comment #2
jhedstromThe regression happened in this commit 134990ead6f69a6b152b1a8f12b22cbad76bc6e6. Also bumping priority since builds done without this get the .info file version set as the revision, which causes scary warnings from the update module about unsupported releases.
Comment #3
jhedstromUpdated patch with tests.
Comment #4
jhedstromCommitted in 6dfb696.
Comment #5
jhedstromThis needs to be committed to 5.x as well.
Comment #6
jhedstromCommitted in 1d3d650.