fix!: require semantic-release v25, node v22.14/v24.10#130
Merged
Conversation
BREAKING CHANGE: Now requires peer dependency `semantic-release@^25` BREAKING CHANGE: Now requires Node.js version ^22.14.0 or ^24.10.0
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
stipsan
approved these changes
Dec 3, 2025
Member
stipsan
left a comment
stipsan
left a comment
There was a problem hiding this comment.
I agree there's no need to support node v20 for build tools like this 👍
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
2 participants
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.
Description
BREAKING CHANGE: Now requires peer dependency
semantic-release@^25BREAKING CHANGE: Now requires Node.js version ^22.14.0 or ^24.10.0
Since this is used as part of CI workflows, I don't think it's super important to support Node.js 20 even though it's still in maintenance LTS. By upgrading, we fix a couple of annoying npm audit warnings.
What to review
Looks good?
Testing
Nothing changed here