Would you please consider using semantic versioning for grunt-eslint?
With your current release pattern, you are iterating the major version (the first number) with every release. In npm terminology, this indicates that you're making breaking changes, and that the new version is not backward compatible with previous versions of the package.
Instead, you could iterate the minor version (the second number) when you're adding new features, but none of the existing functionality is breaking.
Would you please consider using semantic versioning for grunt-eslint? With your current release pattern, you are iterating the major version (the first number) with every release. In npm terminology, this indicates that you're making breaking changes, and that the new version is not backward compatible with previous versions of the package.
Instead, you could iterate the minor version (the second number) when you're adding new features, but none of the existing functionality is breaking.
More information: Semantic versioning and npm Semantic Versioning
Thank you