Skip to content

Support release-it v20? #159

Description

@LeaVerou

Hi! @release-it-plugins/workspaces@6.0.0 declares:

"peerDependencies": { "release-it": "^17.0.0 || ^18.0.0 || ^19.0.0" }

release-it is now at 20.2.1. Every published version of this plugin, up to and including 6.0.0, tops out at ^19:

plugin peer range
4.2.1 ^14 || ^15.2 || ^16 || ^17
5.0.0 – 5.0.3 ^17 || ^18 || ^19
6.0.0 ^17 || ^18 || ^19

So a workspace root that wants both the latest release-it and lockstep workspace releasing gets an ERESOLVE. Minimal repro — a package.json with just those two devDependencies, then npm install:

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error Found: release-it@20.2.1
npm error Could not resolve dependency:
npm error peer release-it@"^17.0.0 || ^18.0.0 || ^19.0.0" from @release-it-plugins/workspaces@6.0.0
npm error   dev @release-it-plugins/workspaces@"^6.0.0" from the root project

The practical effect is that monorepos using this plugin are pinned to release-it 19 indefinitely, and --legacy-peer-deps / --force is the only escape.

Questions:

  1. Is v20 known to be incompatible, or has the peer range simply not been widened yet?
  2. If it is just the range, would you take a PR bumping it to include ^20.0.0?

Happy to test against v20 and send a patch if that would help.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions