phar bundles are a wonderful way to provide a software such as Behat.
Sadly, recent releases are still not available through GitHub downloads.
Perhaps it was forgotten again.
As a workaround, you can create a phar file yourself:
First, fetch Behat sources:
git clone https://github.com/Behat/Behat.git
cd Behat/
composer install
Next, install the box project and build the phar:
curl -LSs https://box-project.github.io/box2/installer.php | php
./box.phar build
indeed (thank you for the tips).
but that would be ever better if such a phar file could be built and provided by @everzet on the official github releases page.
@everzet Any update on this issue?
I tried to set up automatic build of phars on tags via Travis. It's notoriously hard to debug, so help welcome.
In the meantime, you can do it manually as @jakzal describes
@everzet I could have a look one weekend.
@jakzal that would be awesome!
@everzet looks like it's already set up as it should be. The only thing I can currently think of is that the github api key is invalid or not exported.
The following command is able to generate a new key and store it securely inside .travis.yml:
travis setup releases --force
It will reformat your .travis.yml, but you could use it to generate the key, copy it, revert .travis.yml to its current state and add the key back.
WIll try this noon
any news on this?
Another bump to this issue, would love to play around with the framework, but hard to do with no phar :( Working with the latest phar available, but it is rather old...
Do you folks need help in providing phars in each new release?
It would be nice.... currently using a severely outdated version of the suite because of this :(
(not that I am one of the maintainers, just trying to help bump the issue)
https://github.com/Behat/Behat/blob/master/.travis.yml#L40 seems ok.
https://github.com/Behat/Behat/blob/master/box.json seems ok.
https://travis-ci.org/Behat/Behat seems ok.
So I believe GitHub CI ("deploy" job) stopped working at some point.
AFAICT we have no public log from GitHub CI that would let us inspect further what goes wrong.
@everzet / @ciaranmcnulty any plan to solve this that's already 2 years without a phar/usable-release.
Any change to get a fix for this issue soon? Or even a manually build phar & signed phar on the latest release?
If you are interessted I could provide you the setup we are working on in @phpdocumentor to automatically build an publish using github actions.
Was just looking for the phar as well and running into this. Would be great if this could be sorted.
Most helpful comment
Was just looking for the phar as well and running into this. Would be great if this could be sorted.