I'm currently in the process of composerizing a quite old project where I ran into some strange module versions, which seem to have been packaged by drupal, ie.

# Information added by Drupal.org packaging script on 2019-03-28
version: '8.x-3.0-beta1+54-dev'
core: '8.x'
project: 'field_group'
datestamp: 1553812385


# Information added by Drupal.org packaging script on 2017-03-13
version: '8.x-1.1+1-dev'
core: '8.x'
project: 'login_emailusername'
datestamp: 1489402385

In the case of login_emailusername, it turned out that the code of the project is identical to 8.x-1.1 plus 1 follow-up commit from dev, and so could be brought into the project via composer as:

"drupal/login_emailusername": "1.x-dev#f152ee7"

However, I wonder how these modules were "packaged" in these versions, because they don't seem to exist. Maybe someone has an idea? Might this be complete custom syntax or where they maybe imported via drush:make?

  • This also happens for Drupal 7 modules/themes. It's not a question specific to Drupal 8.
    – apaderno
    Commented Mar 15, 2021 at 10:55

1 Answer 1


The 8.x-3.0-beta1+54-dev version means the development snapshot is 54 commits ahead of the 8.x-3.0-beta1 version. Similarly, 8.x-1.1+1-dev means the development snapshot is one commit ahead of the 8.x-1.1 version. Since development snapshots can change much during time, it is probably a way to make better understand how much the development snapshot changed.

Notice that 8.x-3.0-beta1+54-dev is the version reported from the page listing all the installed modules or in the .info file for the module (as you shown, between the lines added by the Drupal.org packaging script).


(The screenshot is for Drupal 7.)

It's not the title you see for a release node in the page showing all the releases (for the Field Group module, in this case), where the release is field_group 8.x-3.x-dev.

To answer your question, it's not a custom syntax. It's the version that the Drupal packaging script adds in the .info file for development snapshot releases, which could then be used in the user interface when showing the installed project version.

The Drupal.org packaging scripts alter the .info file when creating the archive for the project. If the project is copied using Git or Composer, for example, that information is not present, and the version wouldn't appear as 8.x-3.0-beta1+54-dev. (This is also the reason why I took the screenshot from a Drupal 7 instance created on simplytest.me.)


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.