Auto update on packagist

[gianarb]

Hello @thecodeassassin do you have permission to add the packagist's token in order to sync in automatic our update on packagist?

@virgofx thanks for your ping

Thanks a lot
PS at the moment the 1.4.0 is not up to date on packagist

[virgofx]

👍

[virgofx]

ping @thecodeassassin @gianarb

Any way we can get this auto-updated (still having to use custom repository until packagist updates). Just need to get the token from Packagist and add it in the admin settings/webhooks for this Repo. There is a Packagist section (super easy)

[thecodeassassin]

@virgofx i am currently on vacation but will take care of this as soon as possible. sorry for the late reply

[thecodeassassin]

Autoupdate was already enabled, i refreshed the token (maybe that was causing a problem).

[virgofx]

Weird, still shows only the 1.4 version. Must be something going on. I believe you need to have both the correct username and token from your Packagist profile. (The domain isn't necessary) Ensure the github.com setting also has enabled. Then head back to packagist and maybe try to update ...

[thecodeassassin]

@virgofx exactly, i have no idea why it doesn't work. The github service says the payload was delivered successfully :S

[tuupola]

While you are at it, try clicking the green update button in Packagist. I am keen to test the new version.

[tuupola]

What are you using as username in GitHub Packagist hook settings?

[thecodeassassin]

@tuupola the exact username i use on packagist.

[thecodeassassin]

@tuupola updated

[tuupola]

Try changing the GitHub repository address in Packagist to current one. Currently Packagist has https://github.com/influxdb/influxdb-php but it has been changed at some point to https://github.com/influxdata/influxdb-php. Maybe this confuses Packagist.

[virgofx]

Also the composer.json needs to have the name updated as well. New packages don't work unless they match properly.

[virgofx]

I would leave existing packagist as is. Then add a newone with proper name, marked as deprecated in readme. This will give people time to switch composer updates.

[tuupola]

Also the composer.json needs to have the name updated as well. New packages don't work unless they match properly.

This is not true.

The package name has not been changed. Only repository address has been changed. Package name and repository address do not need to match.

Note that I was not talking about package name. I am talking about repository address in Packagist settings.

You can change it by clicking the blue edit button and entering new repository address.

My guess is that webhook comes from different repository than what is in Packagist settings and this causes Packagist to ignore the incoming webhook.