Closed Lalem001 closed 10 years ago
Thanks, @Lalem001. I'll update it now. The annoying thing here is that you're conventionally expected to version it based on the version of brunch that you are using. :/
Just looked over the Brunch FAQ, and it says the following about version numbers:
Brunch x.y.z releases are compatible with plugins (in this case eco-brunch) x.(<= y).*. This means that:
- brunch 1.1.0 with plugin 1.0.0.
- brunch 1.1.0 with plugin 1.1.9.
- brunch 1.9.14 with plugin 1.5.6.
Basically Brunch only really cares about the MAJOR, and MINOR, version numbers. The PATCH number is ignored. Thus your plugin could go to 1.7.9 and it will still be considered compatible.
@Lalem001 I guess that brunch is just trying to enforce semantic versioning by convention as a mapping to plugins then. Thanks for the details here, I'll keep that in mind.
Semantic versioning resolves
1.7.8-hotfix-2
as a lesser version than 1.7.8.According to server.org, a pre-release is:
Thus
-hotfix-2
is telling semver that it is a pre-release for 1.7.8.Would you mind retagging as 1.7.9?