Closed renovate[bot] closed 1 year ago
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:
The artifact failure details are included below:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @ngrx/core@1.2.0
npm ERR! Found: rxjs@6.5.4
npm ERR! node_modules/rxjs
npm ERR! rxjs@"6.5.4" from the root project
npm ERR! rxjs@"6.5.4" from @angular-devkit/schematics@9.1.7
npm ERR! node_modules/@angular-devkit/schematics
npm ERR! @angular-devkit/schematics@"9.1.7" from @angular/cli@9.1.7
npm ERR! node_modules/@angular/cli
npm ERR! dev @angular/cli@"^9.0.4" from the root project
npm ERR! @angular-devkit/schematics@"9.1.7" from @schematics/angular@9.1.7
npm ERR! node_modules/@schematics/angular
npm ERR! @schematics/angular@"9.1.7" from @angular/cli@9.1.7
npm ERR! node_modules/@angular/cli
npm ERR! dev @angular/cli@"^9.0.4" from the root project
npm ERR! 1 more (@schematics/update)
npm ERR! 20 more (@angular-devkit/core, @angular-devkit/architect, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer rxjs@"^5.0.0-beta.12" from @ngrx/core@1.2.0
npm ERR! node_modules/@ngrx/core
npm ERR! @ngrx/core@"^1.2.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: rxjs@5.5.12
npm ERR! node_modules/rxjs
npm ERR! peer rxjs@"^5.0.0-beta.12" from @ngrx/core@1.2.0
npm ERR! node_modules/@ngrx/core
npm ERR! @ngrx/core@"^1.2.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/2023-03-11T07_11_11_225Z-debug-0.log
This PR contains the following updates:
0.6.38
->6.4.0
GitHub Vulnerability Alerts
CVE-2022-21704
Impact
Default file permissions for log files created by the file, fileSync and dateFile appenders are world-readable (in unix). This could cause problems if log files contain sensitive information. This would affect any users that have not supplied their own permissions for the files via the mode parameter in the config.
Patches
Fixed by:
Released to NPM in log4js@6.4.0
Workarounds
Every version of log4js published allows passing the mode parameter to the configuration of file appenders, see the documentation for details.
References
Thanks to ranjit-git for raising the issue, and to @lamweili for fixing the problem.
For more information
If you have any questions or comments about this advisory:
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.