Masterminds / Masterminds/semver

Inconsistency with partial versions

Open
#146 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Go
Stars
1.4k
Forks
168
PR merge metrics
No merged PRs in 30d

Description

This prints true:

c, _ := semver.NewConstraint("2")
v, _ := semver.NewVersion("2.2.3")
fmt.Println(c.Check(v))

While this prints false:

c, _ := semver.NewConstraint("2.2")
v, _ := semver.NewVersion("2.2.3")
fmt.Println(c.Check(v))

Is that intentional? If not I can fire off a PR.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing both Go snippets and tracing how partial constraints are parsed and checked; the issue names no source files or tests. Before changing behavior, confirm with maintainers whether the difference is intentional. Done means the intended semantics are decided and consistently implemented, with regression coverage for both examples.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
tooling
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.