Skip to content
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

Open
mnapoli opened this issue Jan 19, 2017 · 7 comments
Open

Auto-release PHAR from tag #188

mnapoli opened this issue Jan 19, 2017 · 7 comments

Comments

@mnapoli
Copy link
Member

mnapoli commented Jan 19, 2017

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.

@wysow
Copy link
Member

wysow commented Jan 19, 2017

Sure this seems great! Will try to find some time to take a look at it...

@wysow
Copy link
Member

wysow commented Jan 23, 2017

@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 phine/phar which is abandoned...

@wysow
Copy link
Member

wysow commented Jan 23, 2017

Ok box2 project is also using abandoned dependencies, so maybe https://github.com/box-project/box2-lib is the right one...

@mnapoli
Copy link
Member Author

mnapoli commented Jan 23, 2017

@wysow why not call bin/compile directly? It already works today so I don't see why this needs to be changed for the auto-release on Travis

@wysow
Copy link
Member

wysow commented Jan 23, 2017

Sure we can do this, but what about abandoned dependencies? Should we keep them?

@wysow
Copy link
Member

wysow commented Jan 23, 2017

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...

@mnapoli
Copy link
Member Author

mnapoli commented Feb 5, 2017

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants