Open tarlepp opened 6 years ago
Waiting for this to be approved as soon as possible.
In the mean time I will remove this dependency so I can go further with the upgrade process.
@wilson what about new version to packagist ?
@tarlepp I'm asking my colleagues about that right now, and I'll come back with an update.
@wilson thanks for quick reply, I hope that version bump is coming soon - basically this is one of four library that needs updates within SF4 in my project.
@wilson any updates within new version ?
Packagist is still showing old version https://packagist.org/packages/codeclimate/php-test-reporter any ETA when new tag is published ?
Hi @tarlepp.
It sounds like we merged in a change so that it would continue to be possible to depend on the php-test-reporter package in a broader variety of contexts. Is that right? If so, the easiest thing may be to remove the php-test-reporter package entirely, and instead use our new, language-agnostic test reporter. Long-term, our goal is to retire the language-specific test reporters, including this one.
Given that we already merged the PR, we should probably release the change. Doing so requires some amount of QA and re-familiarizing ourself with the deploy process for this package, which isn't an active priority at the moment, although we will try to get to it when we can. In the meantime, will you please try switching to the new test-reporter?
Additional documentation is available here: https://docs.codeclimate.com/docs/configuring-test-coverage
@maxjacobson Hi and first of all thanks for quick and really good reply.
I haven't yet updated to that new reporter, because docs are showing that it's still on beta stage - so that is the reason why I haven't upgraded to that yet. https://docs.codeclimate.com/docs/travis-ci-test-coverage
Any ETA when beta stage is over ?
Any ETA when beta stage is over ?
I don't have an exact date, but I appreciate the reminder. I can say that we don't have any current plans to change the test-reporter's APIs between this beta release and an upcoming stable release.
Any news on this?
Steps required to reproduce the problem
Expected Result
Actual Result