Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency semver to v7.5.2 [security] - autoclosed #912

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 30, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semver 7.3.8 -> 7.5.2 age adoption passing confidence

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

Configuration

📅 Schedule: Branch creation - "" in timezone Europe/Berlin, 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 has been generated by Mend Renovate. View repository job log here.

@codecov
Copy link

codecov bot commented Jun 30, 2023

Codecov Report

Merging #912 (e2af837) into main (68e9df4) will not change coverage.
Report is 1 commits behind head on main.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #912   +/-   ##
=======================================
  Coverage   67.10%   67.10%           
=======================================
  Files          14       14           
  Lines        1988     1988           
  Branches      393      393           
=======================================
  Hits         1334     1334           
  Misses        654      654           

@renovate renovate bot changed the title fix(deps): update dependency semver to v7.5.2 [security] fix(deps): update dependency semver to v7.5.2 [security] - autoclosed Jul 11, 2023
@renovate renovate bot closed this Jul 11, 2023
@renovate renovate bot deleted the renovate/npm-semver-vulnerability branch July 11, 2023 00:59
@renovate renovate bot changed the title fix(deps): update dependency semver to v7.5.2 [security] - autoclosed fix(deps): update dependency semver to v7.5.2 [security] Jul 14, 2023
@renovate renovate bot reopened this Jul 14, 2023
@renovate renovate bot restored the renovate/npm-semver-vulnerability branch July 14, 2023 03:57
@renovate renovate bot force-pushed the renovate/npm-semver-vulnerability branch from 5a79411 to 0f21531 Compare July 14, 2023 03:58
@renovate renovate bot force-pushed the renovate/npm-semver-vulnerability branch 4 times, most recently from c4ca80a to 5b469bc Compare July 30, 2023 09:18
@renovate renovate bot force-pushed the renovate/npm-semver-vulnerability branch from 5b469bc to 9fdc8cd Compare October 23, 2023 22:30
@renovate renovate bot force-pushed the renovate/npm-semver-vulnerability branch from 9fdc8cd to e2af837 Compare November 7, 2023 12:32
@renovate renovate bot changed the title fix(deps): update dependency semver to v7.5.2 [security] fix(deps): update dependency semver to v7.5.2 [security] - autoclosed Nov 7, 2023
@renovate renovate bot closed this Nov 7, 2023
@renovate renovate bot deleted the renovate/npm-semver-vulnerability branch November 7, 2023 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants