Publish release
mtrezza opened this issue · 3 comments
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Feature / Enhancement Description
A new release should be published. Since it's been a long time since the last release, this issue should help us to gather the knowledge about release publishing for the Parse PHP SDK.
From the Parse PHP docs:
- a) Install via git cloning (so it takes this repo as is, with a given tag)
- b) Install via Composer (https://packagist.org/packages/parse/php-sdk) -> it's unclear at this point how a Parse PHP SDK release is published to composer, or even how that package there is managed.
Thanks for opening this issue!
- 🎉 We are excited about your ideas for improvement!
So the composer file seems to be for the packagist registry, which says:
Once you entered your public repository URL in there, your package will be automatically crawled periodically. You just have to make sure you keep the composer.json file up to date.
So this seems to publish automatically when a new tag is created. I have requested the ownership transfer from the registry directly, but if @acinader could transfer ownership that could be easier.
The package has been auto-updated in the packagist registry. Closing this issue, release seems to be have been successful.