Missing module in the "Browse projects" tab - difference between available modules on Drupal.org

The real reason for the discrepancy is that we are actually doing a nightly migration to a Drupal 9 site which hosts the endpoint for the project browser module data. New modules may take a while to show up, or something may fail in the migration.

(In addition to other things, like our filters - we will not show modules that are not compatible with the version of Drupal that's running, and we only show ones by default that have security coverage, etc.)

I will see if Fran can take a look at the migration to check on this.

You can see the project is migrated at https://www.drupal.org/jsonapi/node/project_module?filter[field_project_... →

How project browser is setting up filters for querying might be filtering out the project for some reason.

https://www.drupal.org/jsonapi/node/project_module?filter[field_project_... →

That initially had field_core_semver_maximum: 11000000, that's why it wouldn't show on Drupal 11.1.3.

I re-triggered the semver range calculation and we now have:

field_core_semver_maximum: 12999999,
field_core_semver_minimum: 8000000

So the project should appear now.

The reason for the 12999999 is is because release 2.0.5 of that project has core_version_requirement: ">=8" and we have D12 as max value here.

I think that the issue can be closed as there are no changes required in Project Browser.

I can also confirm this is working now.
The altcha → module was not showing up before, but is now.

Hi,
I confirm this is working now.
Thank you for your analysis. This will indeed help other maintainers understand why their module isn’t showing up in project browser.
Sincerely,
Marc

Fran - I am leaving this open for you, in case there is anything that needs to change on the infra side. But if there's not, or you are tracking it in a separate issue, please mark this Fixed. I have assigned credit.

I reviewed the logic on our end and it really seems ok, so I am going to close this issue. If it were to happen again, I'll implement a workaround that is a one-line change, but only if it's needed.

Automatically closed - issue fixed for 2 weeks with no activity.