We have currently no stable release, so plugin is released under as is basis.
But the current version number representation has no meaning because it is always same '1.6.0-beta'.
And it is not convenient for debubuging / bug report.
So I wrote a PR for rewriting version number with git revision when building plugin in phar format.
Introduction
We have currently no stable release, so plugin is released under as is basis. But the current version number representation has no meaning because it is always same '1.6.0-beta'. And it is not convenient for debubuging / bug report. So I wrote a PR for rewriting version number with git revision when building plugin in phar format.
Behavioural changes
Nothing.
Follow-up