fix: use npm install --legacy-peer-deps to resolve undici conflict#38
Merged
Conversation
…nflict npm ci fails on Node 22 runners because the lock file (generated with npm@11 locally) resolves undici@6.25.0 while npm@10 on CI expects @5.x for certain transitive dependencies. --legacy-peer-deps relaxes peer dep resolution instead of hard-failing on lock file mismatch. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
github-actions Bot
pushed a commit
that referenced
this pull request
May 15, 2026
# [1.1.0](v1.0.9...v1.1.0) (2026-05-15) ### Bug Fixes * force @semantic-release/npm@13.1 via overrides to enable OIDC publish ([#41](#41)) ([ea7f82c](ea7f82c)) * update tool test mocks to capture 5-arg server.tool() signature ([#42](#42)) ([bf499dc](bf499dc)) * use npm install --legacy-peer-deps to resolve undici peer dep conflict ([#38](#38)) ([fcc4bb3](fcc4bb3)) ### Features * add MCP registry metadata for official registry submission ([#34](#34)) ([888dc80](888dc80)) * add tool annotations, MCPB bundle, and smithery config improvements ([#40](#40)) ([818af87](818af87))
|
🎉 This PR is included in version 1.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
npm ciwithnpm install --legacy-peer-depsto fix CI failuresundici@6.25.0, but GitHub Actions Node 22 runners use npm@10 which resolves the same peer deps toundici@5.x—npm cihard-fails on the mismatch--legacy-peer-depsrelaxes peer dep resolution so CI can install without lock file exactness conflictTest plan
npm installwithout lock file errors🤖 Generated with Claude Code