-
-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto-release PHAR from tag #188
Comments
Sure this seems great! Will try to find some time to take a look at it... |
@mnapoli Seems like we will need to find another tool because of this: https://github.com/clue/phar-composer/blob/master/composer.json#L15... I'm searching right now... Maybe https://github.com/box-project/box2 which is the replacement for |
Ok |
@wysow why not call |
Sure we can do this, but what about abandoned dependencies? Should we keep them? |
Another tool we could use is https://github.com/methylbro/compiler (I will try to find time to contribute BTW), it will be released stable on https://github.com/millesime/millesime at some point... |
OK I didn't understand that we are already using abandoned dependencies today. However they still work for now, I'm not against changing that though. Maybe it should be done separately from the auto-release since it's not related? |
I've read this interesting bit on how to generate a phar file in Travis CI and upload it as a GitHub release: https://andreas.heigl.org/2017/01/18/building-a-phar-automated/ That could be applied to Couscous to simplify releasing.
The text was updated successfully, but these errors were encountered: