Fix peer dependency conflicts in semantic-release plugin updates #198
+223
−1,172
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.
The dependency update to
[email protected]introduced peer dependency conflicts that preventednpm cifrom completing. Two plugins were pinned to older major versions incompatible with semantic-release 25.x:Changes
@semantic-release/changelogfrom 5.0.1 → 6.0.3 (requiressemantic-release@>=18.0.0)@semantic-release/release-notes-generatorfrom 9.0.3 → 14.1.0 (requiressemantic-release@>=20.1.0)Both plugins now satisfy their peer dependency constraints with semantic-release 25.x.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.