Closed akovalyov closed 8 years ago
@jakzal ping
I'll work on tagging a stable release soon. Sorry for the delay :)
Can we please get a stable release, really causes me headache because there's no stable release that works with Behat 3.0
Any ETA on this? I just tried to install the extension (using Behat 3.1.5) and got:
Potential causes:
A typo in the package name
The package is not available in a stable-enough version[...]
Thanks.
Can a tag not just be made? The project hasn't had any activity since October so it's not like this project is going to become any more stable any time soon. So why not have a tag which we can use instead of us either having to use dev-master
which is bad practice, use an older version of behat, or not use this?
I just merged #63. If any of you guys could confirm it works with your projects would be fab.
Would be good if you also went through the docs ;) http://behat-page-object-extension.readthedocs.org/en/latest/guide/installation.html
I can confirm it works for me.
Followed instructions on http://behat-page-object-extension.readthedocs.org/en/latest/guide/installation.html. The issue is still there :-( It only works if using dev-master. This did not work: composer require --dev sensiolabs/behat-page-object-extension:^2.0
@dkontorovsky that's not gonna work until we tag the release. Until then use dev-master
. I kindly asked you to review docs as I updated them and want them to be accurate for the release :)
v2.0.0-rc1 was just tagged.
If everyone's fine with rc1 I'll release v2.0.0 in couple of days.
:+1:
Any news on this? It would be great being able to specify a stable version in composer.json :)
@timbordemann it would help if you tested latest version from master :)
I just tagged v2.0.0-rc2
It tells about that user should add
"sensiolabs/behat-page-object-extension": "~2.0"
inrequire-dev
section. However, such release does not exist yet. So, either the version constraint should be changed to2.0.*@dev
in the doc or it is time to tag a new release. @jakzal what do you think?