Feature request: Strict semver versioning e.g. 4.3.0
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 53
- Forks
- 38
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 1
Description
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 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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the repository's release and tag process, along with the Composer version metadata referenced by the issue. Confirm how existing tags are preserved and define completion as publishing future initial minor releases with fully qualified semver tags such as 4.3.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100