I expect the Available Updates report to show all modules. But a particular patched module is missing from the report.
1. Go to simplytest.me
2. For project, type redirect
3. Choose redirect from the pop-up
4. Choose 8.x-1.x-dev as the version
5. Click Advanced options
6. Choose Drupal 11.1.0 as the core version
7. Enter https://git.drupalcode.org/project/redirect/-/merge_requests/127.patch as the patch
8. Click Launch Sandbox
9. Wait for the sandbox creation process to complete and leave you on the welcome page
10. Click log in
11. Log in to site
12. Click Manage, then Extend
13. Type redirect in the filter field
Expected and actual results: Redirect module is checked.
14. Click Reports it the admin menu
15. Click Available updates
Expected result: Available update status is shown for Drupal Core and the Redirect module. If the module does not provide version information in info.yaml, then show "Version number not provided" as the version number. If because of the version number not being provided, the report is unable to determine whether the module is up to date, replace the "Up to date/Update available" message with "Unable to determine".
Actual result: Available update status is shown for Drupal Core. The Redirect module is not listed.
Screenshot of simplytest.me request:
Screenshot of filtered Extend screen:
Screenshot of Available Updates report:
Comments
Comment #2
cilefen commentedThis 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 #3213471: Requiring dev releases with Composer clones the repo, which is different than downloading a dev release archive. Can you confirm?
Comment #3
charles belovI 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.
Comment #4
charles belovComment #5
charles belovComment #6
quietone commentedChanges are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies.
Comment #7
smustgrave commentedWill give one more bump but believe this can be closed as working as designed.
Comment #8
dwwTechnically, I believe the problem here is the lack of a
projectinfo key, notversion. If that assumption is true, #2559313: Parse composer.json for the project name for update module would fix it.Comment #9
cilefen commented