Supported release not showing on project page for distributions

Similar issue with OpenFed distribution: 1.1 is recommended release, but is not displayed anymore in the releases table, only dev snapshot is displayed (before D7 upgrade, both were displayed)

I can also confirm this. The D6 release of OpenAtrium is no longer shown on projects/openatrium. Only the 7.x release and -dev versions are shown.

Confirm. Almost the same with Apachesolr asset and Social comment but releases not shown at all.

The same issue for Panels Tabs module: newly created release 7.x-2.x is not shown in the project page.

Same issue for ERPAL. First we had only the dev snapshot and no alpha5. Then we had randomly changing links on the dev snapshot pointing to just another project. Now we dont have any link on the project page at http://drupal.org/project/erpal

Just pushed an update to https://drupal.org/project/civicrm_starterkit and lost the links to the supported package too. I manually added a link now that #2125795: Update of project info by non-vetted user demotes full projects to sandbox status was resolved, but that's not completely obvious since it's not with the other downloads where users expect it to be.

I'm having the same issue with the first official release of my Commerce Product Clone module not showing in the downloads table. #2130571: New official release not showing in Downloads on project page

Okay ... I think this should get the 'supported' and 'recommended' columns from the edit->releases table working correctly (though it still doesn't address snapshot releases).

Minor improvement. Btw, this is a patch against 'Project' module.

Potential temporary workaround: Edit and save a release node after manipulating the Edit -> Releases table.

The temporary workaround did it for me on two of my modules! Thanks, @jthorson!

@jthorson, this worked for me as well! It took me a minute to figure out what you meant...

1. Click "View all releases"
2. Click the link to the release in question
3. Click "Edit"
4. Reorder the files within "Release files" (not sure if this is required?)
5. Click "Save"
6. Refresh project page and find "Downloads" table updated

Thanks again!

I am happy to report that the workaround in #14 has worked in all the three projects that I manage that were missing releases on the project page:

• Anonymous Publishing
• Flexi Access
• Notify

(I just added a spurious space to the release description before saving.)

You don't even need to change the node ... just re-save it. :)

manuelBS - erpal 7.x-2.0-alpha5 is legitimately not recommended because it includes quicktabs, which has had a more-recent security release. I see you fixed this in dev recently. Please make a new tagged release.

quicktabs 3.4 specifically.

(I'm just going through the linked releases one-by-one now. Please provide a link if something is still broken.)

maximpodorov - looks like 7.x-2.x is there now.

For civicrm_starterkit and other distributions, they get the minimum update status from their packaged projects - 0 = current if they have the latest release of everything, 1 = not current if something is outdated, 2 = something has a more-recent security release.

Currently, the download table filters on = 0. The attached patch relaxes that to <= 1, so we are still making sure distributions package secure projects. It adds a filter on that release being recommended within the branch.

It looks good for my spot-checks on dev, but I want to do more checking on staging when I am more awake.

Seems this affects only distributions now.

Hmz, work-around (re-saving project node) yields unexpected result for my distribution "ferry" (http://drupal.org/project/ferry).

Both the 1.0-rc3 and 1.0 version are displayed as recommend versions on the project page, while obviously I only want to show 1.0 as recommended release (tried re-saving 1.0-rc3 and 1.0 release nodes, but same result)

The edit/releases table only shows 1.0, so I cannot hide 1.0-rc3.

Same w/ https://drupal.org/project/civicrm_starterkit. Tried resaving the release node and updating the supported versions. The dev releases would change, but I'm still not seeing the 4.4-rc4 release.

I am seeing usage https://drupal.org/project/usage/civicrm_starterkit, so something was fixed there. I have a backlog of updates I need to make https://drupal.org/project/cm_starterkit_moderate, so I'll see what happens w/ new releases today.

Deployed #22.

http://drupal.org/project/ferry no longer recommends 1.0-rc3 after re-saving.
https://drupal.org/project/commerce_kickstart now lists 7.x-1.20 under other after re-saving rules 7.x-2.3, which was incorrectly marked as insecure, and re-saving 7.x-1.20.
https://drupal.org/project/civicrm_starterkit now recommends 7.x-4.4-rc4.

I could be missing something, but I think this is fixed.

Thanks, but apparently there is still an issue, now with http://drupal.org/project/openfed

I've re-saved the release node for 1.2 and changed the release table (edit/releases) several times, but only the dev snapshot shows up. 1.2 does not appear in the table on the project page, even though it is the current version in the release table ....

1.2 release does not show up on the project page, because 2 of the modules it includes are marked as "Not secure". This is by design. Related discussion can be found here #2137095: Should supported releases be shown on downloads table even if it contains insecure modules? If so, how?

This is being more actively discussing in #2137095: Should supported releases be shown on downloads table even if it contains insecure modules? If so, how? now.

A few days ago I 7.x-1.2 of Menu Attach Block but it is still not showing on the main module page. Any ideas? I have tried resaving the release node a couple of times.

The version after 7.x-1.11 is 7.x-1.12.

So - I can't release 7.x-1.2?

You can, and it is available for download directly on the release page. But 2 is less than 11, so it is 7 point releases ago when comparing version numbers.

Bing! The penny drops. Thanks!

I have released two version of the modules. still can't see the download table is updated .

My Module is https://www.drupal.org/project/environment_libraries

Thanks,
Ravindra

This is because the releases were marked as security releases. Those are not published without coordination from the security team. There is some help text which mentions https://www.drupal.org/documentation/releases/types when you check that box. In this case, the module only had a dev release up until today, so the module is not covered by the security team, see https://www.drupal.org/security-advisory-policy.

I'm a security team member, so I'll make those non-security releases and publish them.