Support release-it v20?
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
Research direction
Start with the plugin's package.json and inspect the peerDependencies entry for release-it. Reproduce the reported ERESOLVE with a minimal package.json containing release-it 20.2.1 and @release-it-plugins/workspaces 6.0.0, then verify whether the peer range can include ^20. Done means npm install resolves successfully and the plugin's compatibility with release-it v20 has been checked.
Written by the indexing model from the issue text.
Description
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:
- Is v20 known to be incompatible, or has the peer range simply not been widened yet?
- 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.
- Dominant language
- JavaScript
- Stars
- 71
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from release-it-plugins/workspaces
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
release-it-plugins/workspaces#66 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
release-it-plugins/workspaces#40 · 2 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
release-it-plugins/workspaces#36 · 14 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
All issues in release-it-plugins/workspaces
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·
-
client-controller-update ta-bot-triage team-money-movement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MetaMask/metamask-mobile#36594 ·