Skip to content
This repository was archived by the owner on Oct 1, 2025. It is now read-only.

chore(deps): update dependency semver to v7.5.2 [security] - #54

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-semver-vulnerability
Open

chore(deps): update dependency semver to v7.5.2 [security]#54
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-semver-vulnerability

Conversation

@renovate

@renovaterenovateBot commented Mar 6, 2025

Copy link
Copy Markdown
Contributor

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.


This PR contains the following updates:

PackageChangeAgeConfidence
semver7.3.7 -> 7.5.2ageconfidence

GitHub Vulnerability Alerts

CVE-2022-25883

Versions of the package semver before 7.5.2 on the 7.x branch, before 6.3.1 on the 6.x branch, and all other versions before 5.7.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.2

Compare Source

Bug Fixes

v7.5.1

Compare Source

Bug Fixes

v7.5.0

Compare Source

Features
Bug Fixes

v7.4.0

Compare Source

Features
Bug Fixes
Documentation

v7.3.8

Compare Source

Bug Fixes
Documentation
7.3.7 (2022-04-11)
Bug Fixes
Dependencies
7.3.6 (2022-04-05)
Bug Fixes
Documentation
Dependencies

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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovateBotforce-pushed the renovate/npm-semver-vulnerability branch from 4ffe70f to 1cda532CompareMay 19, 2025 15:49
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants