@tsteur opened this Issue on June 10th 2018 Member

image

On October 1st, we otherwise won't receive any new plugins anymore on the Marketplace and neither any plugin updates see https://developer.github.com/changes/2018-04-25-github-services-deprecation/ and https://developer.github.com/apps/differences-between-apps/#about-github-apps/ and https://developer.github.com/webhooks/

October 1st will be soon, especially if something needs to be reviewed or added by Github or something so we should aim to have finished by August 1st maybe? Also considering we need to notify all developers and give them time to upgrade etc. This means we might need to modify our current hook and if the old service is being used, decline the plugin submission and send the author(s) an email update with instructions on how to use the new webhook or app. We should have this active for 1 or 2 months (better 3) so it is really important to finish this as early as possible ideally.

Also we will need to publish a blog post and ideally notify some of the developers (we don't have contact details for all of them) by email and update the marketplace guide etc.

@Findus23 commented on June 10th 2018 Member

Depending on how similar the new GitHub Apps API is to regular webhooks it may make sense to support both on the https://plugins.matomo.org/postreceive-hook (or a similar) endpoint.
That way everyone could simply enable the app without configuration or manually add the webhook if they are using something else than github.

Powered by GitHub Issue Mirror