The version 1.14 is equal to 1.14.0, and I believe this is not something that will likely change, and is also how other package managers I have used handles versioning (both on windows, and on linux). The only accepted (after v 1.0) to include breaking changes is major releases (1.0, 2.0, 3.0, etc), however as I mentioned before not all software developers follow semver v2 (or even v1)īut lets get back on topic, as I already mentioned. If going by the semver v2, then minor releases should also be non-breaking. I am not sure what the behaviour is in terms of minor version, I suppose for the minor version one should either apply the same or explicitly ask the user but the behaviour for patches is much less debatable IMHO
Which adds breaking changes both in minor, patch and build versions. That is only true if the software actually follows semver, I have seen plenty of softwares that do not. I disagree, ff I specified 1.14.0 explicitly, yes, but the expectation is that if the full version is not specified the latest patched version is used.Ī full version would be a 4 part version, meaning that you would have needed to specify 1.14.0.0 to get the actual version (yes, there are plenty of softwares still using all 4 parts).Įspecially for patches, they are by definition not breaking and therefore in the majority of the cases the users wants to use the latest patched version and in terms of security best practices, chocolatey should recommend this as well.
0 kommentar(er)
