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
Notice the breaking changes on the commit April 17th.
Do you have a strategy for introducing breaking changes? How should someone use this lib without risking future breaks?
The text was updated successfully, but these errors were encountered:
A good way of making changes to library would be to keep a tagged version, so people using your library won't have this issues in the future.
This compromises also the trust on systems like composer.
Sorry, something went wrong.
yes we need to start using tags
No branches or pull requests
Notice the breaking changes on the commit April 17th.
Do you have a strategy for introducing breaking changes? How should someone use this lib without risking future breaks?
The text was updated successfully, but these errors were encountered: