Hi - I was wondering if for future releases it'd be possible to stick to fully qualified semver versions. When working with composer (and subsequently tools like dependabot) having the following tags makes it difficult to use version constraints reliably:
4.3 - if I use "~4.3" as a version constraint I'll get any 4.x release
4.1.2 - if I use "~4.1.2" as a version constraint I'll get any 4.1.x release
It'd be great if the initial minor version releases could be fully qualified e.g. 4.3.0.
For a package manager like composer referencing ~4.3 etc... would still work, the only issue would be if anyone was referencing the 4.3 tag directly but as long as no existing tags are removed it should be a safe change.
Hi - I was wondering if for future releases it'd be possible to stick to fully qualified semver versions. When working with composer (and subsequently tools like dependabot) having the following tags makes it difficult to use version constraints reliably:
4.3- if I use "~4.3" as a version constraint I'll get any 4.x release4.1.2- if I use "~4.1.2" as a version constraint I'll get any 4.1.x releaseIt'd be great if the initial minor version releases could be fully qualified e.g.
4.3.0.For a package manager like composer referencing
~4.3etc... would still work, the only issue would be if anyone was referencing the 4.3 tag directly but as long as no existing tags are removed it should be a safe change.