Masterminds / Masterminds/semver
Rationale for ~0.0.0 being equal to >=0.0.0?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 168
- PR merge metrics
- No merged PRs in 30d
Description
I noticed that this library treats the ~0.0.0 constraint as equal to >=0.0.0 (all versions are valid against the constraint) and was implemented in https://github.com/Masterminds/semver/commit/429e95e30a373ced3c657c4419bc65aa0fffc1f6. Before seeing this I was thinking that 0.1.0 and greater would fail the constraint against ~0.0.0. I couldn't find any rationale for this decision and wondering if any additional context could be provided.
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing commit 429e95e30a373ced3c657c4419bc65aa0fffc1f6 and the existing handling of the ~0.0.0 constraint. Done means the rationale for treating it like >=0.0.0 is established and recorded in the issue or appropriate project documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100