We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For 2.0.1 we made a mistake in composer.json's version field resulting in v2.0.1 not being published (ref. https://medium.com/packagist/tagged-a-new-release-for-composer-and-it-wont-show-up-on-packagist-org-or-on-private-packagist-efaf21c212ff). Let's have dev tool that handles this for us so we won't make the same mistake.
composer.json
version
The text was updated successfully, but these errors were encountered:
@ellennugroho do u wanna take this?
Sorry, something went wrong.
sure
ellennugroho
No branches or pull requests
For 2.0.1 we made a mistake in
composer.json
'sversion
field resulting in v2.0.1 not being published (ref. https://medium.com/packagist/tagged-a-new-release-for-composer-and-it-wont-show-up-on-packagist-org-or-on-private-packagist-efaf21c212ff). Let's have dev tool that handles this for us so we won't make the same mistake.The text was updated successfully, but these errors were encountered: