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
Maybe after this overhaul we should start from v2.0.0 as the 1st tag? We can do that by creating a "Releases" for the current state.
The text was updated successfully, but these errors were encountered:
If the previous version was (for example) v1.1.0, then this one would probably be v1.2.0, since there are no breaking changes (in the semver sense)
But I agree, perhaps GH Releases is a good idea (I guess?). I rarely use it, so I don't know enough
Sorry, something went wrong.
I guess GH Releases automatically creates a tag as well. Having a tag helps to download the library from a CDN btW.
No branches or pull requests
Maybe after this overhaul we should start from v2.0.0 as the 1st tag?
We can do that by creating a "Releases" for the current state.
The text was updated successfully, but these errors were encountered: