Skip to content
This repository was archived by the owner on Jan 3, 2023. It is now read-only.

Update dependency jpeg-js to 0.4.4 [SECURITY] (master)#447

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/master-npm-jpeg-js-vulnerability
Open

Update dependency jpeg-js to 0.4.4 [SECURITY] (master)#447
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/master-npm-jpeg-js-vulnerability

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate Bot commented Jun 17, 2022

Mend Renovate

This PR contains the following updates:

Package Change
jpeg-js 0.4.3 -> 0.4.4

GitHub Vulnerability Alerts

CVE-2022-25851

The package jpeg-js before 0.4.4 is vulnerable to Denial of Service (DoS) where a particular piece of input will cause the program to enter an infinite loop and never return.


Configuration

📅 Schedule: Branch creation - "" in timezone America/New_York, 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.

@renovate
Copy link
Copy Markdown
Author

renovate Bot commented Jun 17, 2022

⚠ 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
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @storybook/addon-actions@6.4.22
npm ERR! Found: react@18.0.0
npm ERR! node_modules/react
npm ERR!   react@"^18.0.0" from the root project
npm ERR!   peer react@">=16.3.0" from @emotion/core@10.3.0
npm ERR!   node_modules/@emotion/core
npm ERR!     peer @emotion/core@"^10.0.27" from @emotion/styled@10.3.0
npm ERR!     node_modules/@emotion/styled
npm ERR!       @emotion/styled@"^10.0.27" from @storybook/theming@6.4.22
npm ERR!       node_modules/@storybook/addon-actions/node_modules/@storybook/theming
npm ERR!         @storybook/theming@"6.4.22" from @storybook/addon-actions@6.4.22
npm ERR!         node_modules/@storybook/addon-actions
npm ERR!         3 more (@storybook/addons, @storybook/api, @storybook/components)
npm ERR!       18 more (@storybook/theming, @storybook/theming, ...)
npm ERR!     peer @emotion/core@"^10.0.28" from @emotion/styled-base@10.3.0
npm ERR!     node_modules/@emotion/styled-base
npm ERR!       @emotion/styled-base@"^10.3.0" from @emotion/styled@10.3.0
npm ERR!       node_modules/@emotion/styled
npm ERR!         @emotion/styled@"^10.0.27" from @storybook/theming@6.4.22
npm ERR!         node_modules/@storybook/addon-actions/node_modules/@storybook/theming
npm ERR!         18 more (@storybook/theming, @storybook/theming, ...)
npm ERR!     29 more (@storybook/theming, @storybook/theming, ...)
npm ERR!   14 more (@emotion/styled, @emotion/styled-base, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional react@"^16.8.0 || ^17.0.0" from @storybook/addon-actions@6.4.22
npm ERR! node_modules/@storybook/addon-actions
npm ERR!   dev @storybook/addon-actions@"^6.4.18" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@17.0.2
npm ERR! node_modules/react
npm ERR!   peerOptional react@"^16.8.0 || ^17.0.0" from @storybook/addon-actions@6.4.22
npm ERR!   node_modules/@storybook/addon-actions
npm ERR!     dev @storybook/addon-actions@"^6.4.18" 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-06-17T03_51_12_778Z-debug-0.log

Sign up for free to 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.

1 participant