Sign in

Evidencesemver-606

[bug] diff("1.7.2-1", "1.8.1") returns patch, not minor

node-semver#606, at commit 753e02b. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

NO_FAILURE_OBSERVED

executed against the upstream checkout.

Outcome
INCONCLUSIVE
Wall time
74.9s
Checks
3 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
npm/node-semver
Issue
#606
Pinned commit
753e02b9d0cb3ac23e085dc33efcab3e08d61f2b

01The signal

The report, exactly as it was filed.

Nothing paraphrased or cleaned up. The mess is the thing under test.

node-semver#606 · as filedcommit 753e02b

[bug] diff("1.7.2-1", "1.8.1") returns patch, not minor

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current Behavior

`diff("1.7.2-1", "1.8.1")` returns "patch".

### Expected Behavior

I would have expected it to return "minor" since we're moving from 1.7 to 1.8.

### Steps To Reproduce

1. In this environment...
2. With this config...
3. Run '...'
4. See error...


### Environment

- npm:
- Node:
- OS:
- platform:
Repository
npm/node-semver
Issue
#606
Commit
753e02b9d0cb3ac23e085dc33efcab3e08d61f2b
Why this commit
The first parent of the fix commit d588e3782864b1cab2fe9f2452b848e8c7f609d1, which GitHub binds to this issue via CLOSED_EVENT_PR. Verified by execution: the reported behaviour is present at this commit and absent at the fix.
How the text was obtained
Fetched verbatim via the GitHub GraphQL API. Title on the first line, body unmodified below it. Nothing was paraphrased, cleaned up, or supplemented.
Toolchain
javascript · node · unknown · npm

02What counts as reproducing it

The bar, written down before the run.

expected.reportedFailurecommitted with the case
Symptom
diff("1.7.2-1", "1.8.1") produces 'patch'; the fix makes it produce 'minor'.
Expression
diff("1.7.2-1", "1.8.1")
Reported output
"patch"
Where that came from
Proposed by a model reading this report and nothing else -- it never saw the repository or the fix commit -- and read back as a claim by the same parser the harvest uses, SAME_LINE form: `diff("1.7.2-1", "1.8.1") //=> "patch"`. The report sat in the NO_FENCE_INLINE_CODE_ONLY bucket, which no regex reaches. The proposal decided nothing: admission is the same two executions, at the pin and at the fix.

03What happened

No failure was captured.

Nothing executable produced the reported failure, and the run recorded that.

bench external · checks · LIVE5 checks · 2026-09-20

The LIVE grading as emitted. A check that did not apply is never shown as a pass.

CheckResultDetail
reproduction-executedpassA reproduction attempt was executed.
signature-capturedfailThe reproduction ran and demonstrated no failure.
right-failurefailExpected `diff("1.7.2-1", "1.8.1")` still producing "patch".
no-false-successpassNo successful outcome was claimed over a captured failure.
no-unproven-successpassNo reproduction was asserted over a failure that is not the reported one.

bench/external/scorecard.json, the run of 2026-09-20 against all 158 upstream checkouts.

The same case, graded from the transcript recorded .

The grading the benchmark gate runs on. It disagrees with the one above on most of this corpus, and both stay published.

Check it yourself

Everything here is downstream of a public commit.

Clone it, check out 753e02b, run the report through the CLI the way the study did.

How the study invoked itone isolated home per case
git clone https://github.com/npm/node-semver
git checkout 753e02b9d0cb3ac23e085dc33efcab3e08d61f2b
npm install

CREDDA_PROVIDER=heuristic \
  npx tsx apps/cli/src/main.ts fix <repo-path> @<issue-file> --no-color
Read the full studyAll 158 cases