# What changed in parse-conflict-json

> 4 changes in parse-conflict-json 3 to 6 from its official release notes, upgrade guides and advisories: 4 breaking. Each one cited. Sources checked 2026-10-27. HTML: https://unstale.sh/npm/parse-conflict-json/

To see which of these apply to a repository, run `npx @unstale/cli init` in it.

## parse-conflict-json 6

### Breaking changes

- The supported Node.js versions are now ^22.22.2 || ^24.15.0 || >=26.0.0. (6.0.0) — [release notes](https://github.com/npm/parse-conflict-json/releases/tag/v6.0.0)

## parse-conflict-json 5

### Breaking changes

- The supported Node.js versions are now ^20.17.0 || >=22.9.0, so developers must use a compatible runtime. (5.0.0) — [release notes](https://github.com/npm/parse-conflict-json/releases/tag/v5.0.0)

## parse-conflict-json 4

### Breaking changes

- The supported Node.js versions are now ^18.17.0 or >=20.5.0, so developers must use a compatible runtime. (4.0.0) — [release notes](https://github.com/npm/parse-conflict-json/releases/tag/v4.0.0)

## parse-conflict-json 3

### Breaking changes

- Node.js compatibility is now limited to ^14.17.0 || ^16.13.0 || >=18.0.0. (3.0.0) — [release notes](https://github.com/npm/parse-conflict-json/releases/tag/v3.0.0)