Packagist: Package API response outdated

Created on 3 Sep 2016 · 6Comments · Source: composer/packagist

Hi, yesterday I have tagged a new version v0.3.0 (https://packagist.org/packages/fusio/engine) but this version is not showing up in the API response (https://packagist.org/p/fusio/engine.json). Is this maybe a caching problem?

Source

chriskapp

Most helpful comment

Hi, since yesterday evening, I have the same issues. Commits (tags or dev-master) do show on my Packagist account, but the API is clearly outdated. Thus, Composer thinks there is no updates.

I have checked on twitter for any feedback from packagist, but they don't mention anything. Thanks to this issue report, they may have a look and recreate the Packagist index.

By the way, I have already erased the Composer .cache folder, and tried on several website I own, the API response from Packagist is outdated on any website when queried from Composer (or directly through an packagist.org/vendor/name.json url).

It seems their indexing robot has stopped working !

net-tools on 3 Sep 2016

👍3

All 6 comments

I was unable to get new packages (created yesterday) to show up on the API or to be recognized by composer.

runz0rd on 3 Sep 2016

Hi, since yesterday evening, I have the same issues. Commits (tags or dev-master) do show on my Packagist account, but the API is clearly outdated. Thus, Composer thinks there is no updates.

I have checked on twitter for any feedback from packagist, but they don't mention anything. Thanks to this issue report, they may have a look and recreate the Packagist index.

It seems their indexing robot has stopped working !

net-tools on 3 Sep 2016

👍3

I'm also having the same with with milesasylum/schnoop-schema.

The package is reflecting updates on the website, but the API is supplying outdated information.