Problem/Motivation

If I installed a development version of a module, that module does not show up on the updates report.

Steps to reproduce

1. Go to simplytest.me in three browser tabs
2. In the first browser tab, choose the current release of admin_toolbar (3.6.3)
3. In the second browser tab, choose the 3.x-dev version of admin_toolbar (3.x-dev)
4. In the third browser tab, choose Drupal core current release (11.4.4)
5. Create all three sites
6. Go to /admin/modules in each tab
7. Filter on the word toolbar

Expected and actual results: Admin Toolbar module only shows up on the first two browser tabs

8. Go to /admin/reports/updates in each tab

Expected result: On the first and second tabs, there are two items listed, Drupal Core and Admin Toolbar. On the third tab, there is one item listed, Drupal Core.

Actual result: On the first tab, there are two items listed, Drupal Core and Admin Toolbar. On the second and third tab, there is one item listed, Drupal Core.

Proposed resolution

Show development versions on the update report.

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Comments

charles belov created an issue. See original summary.

cilefen’s picture

cilefen commented
Status: Active » Postponed (maintainer needs more info)
Issue tags: +Possible duplicate
Related issues: +#2559313: Parse composer.json for the project name for update module

I think this is a duplicate of #2559313: Parse composer.json for the project name for update module, which is from the even older #1013302: Composer metadata on dev versions doesn't work in update.php.

@charles belov, please verify that.

charles belov’s picture

charles belov
he/him
Primary language English
Location San Francisco, CA, US
commented

[removed comment that I was unable to respond - I realized I could download the files and check what was in the info.yml file]

I believe it is not a duplicate. If I do parallel installs into simplytest.me of the production and dev versions, they are both installed using git. Yet the production version does show in the update report. If it were a duplicate, I would expect either neither to work or both to work.

I believe the issue here is either the parsing of the version name or a change to the composer.json file. I do quality assurance, not development, and the implications of the issue you refer to are not part of my skill set, so I could be mistaken. Hopefully the information below will be helpful to you to determine whether or not this is a duplicate issue.

The production version of admin_toolbar (3.6.3) has a file admin_toolbar.info.yml containing the following lines:

# Information added by Drupal.org packaging script on 2025-12-30
version: '3.6.3'
project: 'admin_toolbar'
datestamp: 1767127271

The dev version of admin_toolbar (3.x-dev) has a file admin_toolbar.info.yml containing the following lines:

# Information added by Drupal.org packaging script on 2026-07-10
version: '3.6.3+10-dev'
project: 'admin_toolbar'
datestamp: 1783688434

So, when the dev version of admin_toolbar is installed, I would expect the available updates report to show an entry for admin_toolbar version 3.6.3+10-dev rather than no entry at all.

I also did a compare of the composer.json files.

The production version of admin_toolbar (3.6.3) has a composer.json file containing the following lines:

"conflict": {
    "drupal/project_browser": "<2.1.0"
  }

The dev version of admin_toolbar (3.x-dev) has a composer.json file containing the following lines:

"conflict": {
        "drupal/automatic_updates": "<4",
        "drupal/project_browser": "<2.1.0"
    }

Aside from going from 2 space indents to 4 space indents throughout, there are no other changes in the composer.json file. The composer.json file contains no version information in either the release or the dev version.

charles belov’s picture

charles belov
he/him
Primary language English
Location San Francisco, CA, US
commented
Status: Postponed (maintainer needs more info) » Active