node-sdk icon indicating copy to clipboard operation
node-sdk copied to clipboard

chore(deps): update dependency trim-newlines to 3.0.1 [security]

Open renovate[bot] opened this issue 4 years ago • 3 comments

Mend Renovate

This PR contains the following updates:

Package Change
trim-newlines 2.0.0 -> 3.0.1

GitHub Vulnerability Alerts

CVE-2021-33623

@​rkesters/gnuplot is an easy to use node module to draw charts using gnuplot and ps2pdf. The trim-newlines package before 3.0.1 and 4.x before 4.0.1 for Node.js has an issue related to regular expression denial-of-service (ReDoS) for the .end() method.


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, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

renovate[bot] avatar Jan 26 '22 20:01 renovate[bot]

Codecov Report

Merging #1143 (d551a35) into master (709720d) will decrease coverage by 88.89%. The diff coverage is n/a.

:exclamation: Current head d551a35 differs from pull request most recent head 010789a. Consider uploading reports for the commit 010789a to get more accurate results

@@            Coverage Diff             @@
##           master   #1143       +/-   ##
==========================================
- Coverage   88.88%       0   -88.89%     
==========================================
  Files           1       0        -1     
  Lines           9       0        -9     
  Branches        2       0        -2     
==========================================
- Hits            8       0        -8     
+ Misses          1       0        -1     

see 1 file with indirect coverage changes

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

codecov-commenter avatar Feb 16 '22 19:02 codecov-commenter

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
Found file in cache: /tmp/renovate-cache/buildpack/7576b42decc67f70b61585f41c5074bea75c260886346e567578ea0e0dc2d571/node-v16.17.0-linux-x64.tar.xz
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/tslint
npm ERR!   dev tslint@"^6.1.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer tslint@"^5.0.0" from [email protected]
npm ERR! node_modules/tslint-eslint-rules
npm ERR!   dev tslint-eslint-rules@"^5.4.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/tslint
npm ERR!   peer tslint@"^5.0.0" from [email protected]
npm ERR!   node_modules/tslint-eslint-rules
npm ERR!     dev tslint-eslint-rules@"^5.4.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-08-16T21_57_39_094Z-debug-0.log

renovate[bot] avatar Mar 08 '22 04:03 renovate[bot]

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

CLAassistant avatar Aug 16 '22 21:08 CLAassistant