Open renovate[bot] opened 2 years 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 WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @sonia-corporation/rpg-character@1.0.0
npm WARN Found: semantic-release@17.4.7
npm WARN node_modules/semantic-release
npm WARN dev semantic-release@"19.0.0" from the root project
npm WARN 6 more (@semantic-release/changelog, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer semantic-release@">=15.8.0 <18.0.0" from @semantic-release/changelog@5.0.1
npm WARN node_modules/@semantic-release/changelog
npm WARN dev @semantic-release/changelog@"5.0.1" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @sonia-corporation/rpg-character@1.0.0
npm WARN Found: semantic-release@17.4.7
npm WARN node_modules/semantic-release
npm WARN dev semantic-release@"19.0.0" from the root project
npm WARN 6 more (@semantic-release/changelog, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/git@9.0.1
npm WARN node_modules/@semantic-release/git
npm WARN dev @semantic-release/git@"9.0.1" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @sonia-corporation/rpg-character@1.0.0
npm WARN Found: semantic-release@17.4.7
npm WARN node_modules/semantic-release
npm WARN dev semantic-release@"19.0.0" from the root project
npm WARN 6 more (@semantic-release/changelog, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/github@7.2.3
npm WARN node_modules/@semantic-release/github
npm WARN dev @semantic-release/github@"7.2.3" from the root project
npm WARN 1 more (semantic-release)
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: @sonia-corporation/rpg-character@1.0.0
npm ERR! Found: semantic-release@19.0.0
npm ERR! node_modules/semantic-release
npm ERR! dev semantic-release@"19.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/github@7.2.3
npm ERR! node_modules/@semantic-release/github
npm ERR! dev @semantic-release/github@"7.2.3" 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-02-09T09_19_26_576Z-debug.log
This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.
This PR contains the following updates:
2.1.3
->4.0.10
GitHub Vulnerability Alerts
CVE-2022-21680
Impact
What kind of vulnerability is it?
Denial of service.
The regular expression
block.def
may cause catastrophic backtracking against some strings. PoC is the following.Who is impacted?
Anyone who runs untrusted markdown through marked and does not use a worker with a time limit.
Patches
Has the problem been patched?
Yes
What versions should users upgrade to?
4.0.10
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Do not run untrusted markdown through marked or run marked on a worker thread and set a reasonable time limit to prevent draining resources.
References
Are there any links users can visit to find out more?
For more information
If you have any questions or comments about this advisory:
CVE-2022-21681
Impact
What kind of vulnerability is it?
Denial of service.
The regular expression
inline.reflinkSearch
may cause catastrophic backtracking against some strings. PoC is the following.Who is impacted?
Anyone who runs untrusted markdown through marked and does not use a worker with a time limit.
Patches
Has the problem been patched?
Yes
What versions should users upgrade to?
4.0.10
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Do not run untrusted markdown through marked or run marked on a worker thread and set a reasonable time limit to prevent draining resources.
References
Are there any links users can visit to find out more?
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 is behind base branch, 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.