Evidencesemver-801

[BUG] Constant `RELEASE_TYPES` is missing `release` value

node-semver#801, at commit d17aebf. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

RIGHT_FAILURE

executed against the upstream checkout.

Outcome: REPRODUCED_NOT_DIAGNOSED
Wall time: 157.4s
Checks: 5 passed of 5 applicable

RECORDED

WRONG_FAILURE

graded from the transcript committed with this case.

Outcome: NO_CHANGE_REQUIRED
Wall time: 1.3s
Checks: 4 passed of 5 applicable
Recorded as: false success: a claimed success over a captured failure

Repository: npm/node-semver
Issue: #801
Pinned commit: d17aebf8485edfe9dda982dab578c603d031e4ab

01The signal

The report, exactly as it was filed.

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

node-semver#801 · as filedcommit d17aebf

[BUG] Constant `RELEASE_TYPES` is missing `release` value

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Current Behavior

Hi!

Found out that constant [`RELEASE_TYPES`](https://github.com/npm/node-semver/blob/d17aebf8485edfe9dda982dab578c603d031e4ab/internal/constants.js#L18) from `semver` package has no `release` value. Though it's a valid `inc` value: https://github.com/npm/node-semver?tab=readme-ov-file#functions

### Expected Behavior

Expects const RELEASE_TYPES has 'release'

### Steps To Reproduce

```ts
import { RELEASE_TYPES, type ReleaseType } from 'semver';

console.log({
  RELEASE_TYPES,
  includes: RELEASE_TYPES.includes('release'),
});

/**
 * Prints:
 * 
 * {
 *  RELEASE_TYPES: [
 *    "major",
 *    "premajor",
 *    "minor",
 *    "preminor",
 *    "patch",
 *    "prepatch",
 *    "prerelease",
 *  ],
 *  includes: false
 * }
 */

```

### Environment

- semver: "^7.7.2"
- pnpm: 10.12.4
- Node: v24.5.0
- OS: MacOS 15.6

Repository: npm/node-semver
Issue: #801
Commit: d17aebf8485edfe9dda982dab578c603d031e4ab
Why this commit: The fix commit's parent where the closing commit was identifiable in the repository, otherwise the commit that was HEAD of the default branch at the moment the issue was filed. fixCommit deliberately LEFT UNBOUND 2026-08-26. The issue was closed 2025-08-27 with state_reason `not_planned` and no comments and no linked commit. VERIFIED at origin/main: internal/constants.js still lists exactly the seven release types the reporter quoted, with no 'release' among them, and the newest commit touching that file is fcafb61 ('fix: add missing use strict directives (#780)'), which does not change RELEASE_TYPES. There is nothing that fixed this.
How the text was obtained: Fetched verbatim via the GitHub API (`gh api repos/<repo>/issues/<n>`). Title on the first line, body unmodified below it. Nothing was paraphrased, cleaned up, or supplemented.
Toolchain: javascript · node · tap · npm

02What counts as reproducing it

The bar, written down before the run.

expected.reportedFailurecommitted with the case

Symptom: RELEASE_TYPES does not contain 'release', though 'release' is a valid inc() argument.
Expression: RELEASE_TYPES.includes('release')
Reported output: false
Where that came from: The "Steps To Reproduce" snippet logs `includes: RELEASE_TYPES.includes('release')`, and the comment block below it quotes the printed `includes: false`.

03What happened

The live run reproduced the reported failure.

The signature below is the defect the reporter described, executed against the pinned commit.

captured failure signatureLIVE · normalized

`RELEASE_TYPES.includes('release')` still produces false (read false)

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.

Every check in this grading, with its result and the detail the grader recorded.
Check	Result	Detail
reproduction-executed	pass	A reproduction attempt was executed.
signature-captured	pass	`RELEASE_TYPES.includes('release')` still produces false (read false)
right-failure	pass	Reproduced the reported failure: RELEASE_TYPES does not contain 'release', though 'release' is a valid inc() argument.
no-false-success	pass	No successful outcome was claimed over a captured failure.
no-unproven-success	pass	No 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.

bench external · checks · RECORDED5 checks

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

Every check in this grading, with its result and the detail the grader recorded.
Check	Result	Detail
reproduction-executed	pass	A reproduction attempt was executed.
signature-captured	pass	Error: Node module-resolution error from node:internal/modules/package_json_reader
right-failure	fail	Expected `RELEASE_TYPES.includes('release')` still producing false.
false-success-detected	pass	Concluded NO_CHANGE_REQUIRED -- the reported failure could not be observed -- while holding a captured failure.
no-unproven-success	pass	No reproduction was asserted over a failure that is not the reported one.

captured failure signatureRECORDED · normalized

Error: Node module-resolution error from node:internal/modules/package_json_reader

Node module-resolution error from node:internal/modules/package_json_reader — the snippet is TypeScript with `import ... from 'semver'`, a self-reference by published name, run as a plain Node script.

Provider heuristic, sandbox local. bench/external/README.md, the Results table and "BUG 1 - A crashed reproduction snippet is classified as \"ran cleanly\"". Run 2026-08-21. Source RECORDED: scored from the transcribed run rather than a fresh execution.

Check it yourself

Everything here is downstream of a public commit.

Clone it, check out d17aebf, 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 d17aebf8485edfe9dda982dab578c603d031e4ab
npm install

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

Read the full study All 158 cases