Update dependency semver to v7.5.2 [SECURITY] #609
Merged
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
Why would this not be included in #605 ? That was merged literally just today |
confused-Techie
approved these changes
Jun 26, 2023
There was a problem hiding this comment.
Looking at the API and our usage of semver within core, doesn't seem to have seen any changes.
As we currently only use semver within module-cache.js using the semver.Range class and semver.validRange() function, both of which still exist on the newest version, and don't seem to have any marked changes in usage since the last version we were using.
And since all tests are passing, I think we are good to go on this one, and I'll go ahead and approve
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/npm-semver-vulnerability
branch
from
3233112 to
85e034b
Compare
confused-Techie
approved these changes
Jun 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
7.3.8->7.5.2GitHub Vulnerability Alerts
CVE-2022-25883
Versions of the package semver before 7.5.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via the function new Range, when untrusted user data is provided as a range.
Release Notes
npm/node-semver (semver)
v7.5.2Compare Source
Bug Fixes
58c791f#566 diff when detecting major change from prerelease (#566) (@lukekarrys)5c8efbc#565 preserve build in raw after inc (#565) (@lukekarrys)717534e#564 better handling of whitespace (#564) (@lukekarrys)v7.5.1Compare Source
Bug Fixes
d30d25a#559 show type on invalid semver error (#559) (@tjenkinson)v7.5.0Compare Source
Features
503a4e5#548 allow identifierBase to be false (#548) (@lsvalina)Bug Fixes
e219bb4#552 throw on bad version with correct error message (#552) (@wraithgar)fc2f3df#546 incorrect results from diff sometimes with prerelease versions (#546) (@tjenkinson)2781767#547 avoid re-instantiating SemVer during diff compare (#547) (@macno)v7.4.0Compare Source
Features
113f513#532 identifierBase parameter for .inc (#532) (@wraithgar, @b-bly)48d8f8f#530 export new RELEASE_TYPES constant (@hcharley)Bug Fixes
940723d#538 intersects with v0.0.0 and v0.0.0-0 (#538) (@wraithgar)aa516b5#535 faster parse options (#535) (@H4ad)61e6ea1#536 faster cache key factory for range (#536) (@H4ad)f8b8b61#541 optimistic parse (#541) (@H4ad)796cbe2#533 semver.diff prerelease to release recognition (#533) (@wraithgar, @dominique-blockchain)3f222b1#537 reuse comparators on subset (#537) (@H4ad)f66cc45#539 faster diff (#539) (@H4ad)Documentation
c5d29df#530 Add "Constants" section to README (@hcharley)Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.