- Issue created by @charles belov
This is the expected behavior of the update module when there is no version set in the info.yaml file. If you select a branch release like that, Git will clone the project repo rather than download a versioned compressed archive.
This isn't a Drupal Core bug but rather more like ✨ Requiring dev releases with Composer clones the repo, which is different than downloading a dev release archive Active . Can you confirm?
- 🇺🇸United States charles belov San Francisco, CA, US
I am QA, not a developer, so I am not able to comment on the relevance of the other issue.
I disagree that just not showing the module is an appropriate result of the version being missing from the info.yaml file for the module. I believe the correct behavior would be to show the module in the report; wherever version info was missing, the report would show "Missing" rather than a version number.
Just not showing the module at all makes the report look broken. In a long report, it could lead to incorrect assumptions about the current website.
Updating the issue description to show a new expected result.
- 🇳🇿New Zealand quietone
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .