Skip to content

Update dependency copy-webpack-plugin to v7#44

Open
dev-mend-for-github-com[bot] wants to merge 1 commit intotrunkfrom
whitesource-remediate/copy-webpack-plugin-7.x
Open

Update dependency copy-webpack-plugin to v7#44
dev-mend-for-github-com[bot] wants to merge 1 commit intotrunkfrom
whitesource-remediate/copy-webpack-plugin-7.x

Conversation

@dev-mend-for-github-com
Copy link
Copy Markdown

@dev-mend-for-github-com dev-mend-for-github-com bot commented Jan 14, 2025

This PR contains the following updates:

Package Type Update Change
copy-webpack-plugin dependencies major 6.4.17.0.0

By merging this PR, the issue #13 will be automatically resolved and closed:

Severity CVSS Score Vulnerability Reachability
Critical Critical 9.8 CVE-2022-37601
High High 8.2 CVE-2021-37701
High High 8.2 CVE-2021-37713
High High 7.5 CVE-2022-37603
High High 7.1 CVE-2022-46175
Medium Medium 5.3 CVE-2024-4067

Release Notes

webpack/copy-webpack-plugin (copy-webpack-plugin)

v7.0.0

Compare Source

⚠ BREAKING CHANGES
  • minimum supported webpack version is 5
  • the flatten option was removed in favor [name].[ext] value for the to option,
  • the transformPath option was removed in favor Function type of the to option, look at examples
  • the cacheTransform option was removed in favor Object type of the transform option, look at examples
  • migration on the compilation.hooks.processAssets hook
  • empty filtered paths throw an error, you can disable this behaviour using the noErrorOnMissing option

  • If you want to rebase/retry this PR, check this box

@dev-mend-for-github-com dev-mend-for-github-com bot added the security fix Security fix generated by Mend label Jan 14, 2025
@dev-mend-for-github-com
Copy link
Copy Markdown
Author

⚠️ 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: src/Administration/Resources/app/administration/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: administration@1.0.0
npm ERR! Found: webpack@4.46.0
npm ERR! node_modules/webpack
npm ERR!   webpack@"4.46.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^5.1.0" from copy-webpack-plugin@7.0.0
npm ERR! node_modules/copy-webpack-plugin
npm ERR!   copy-webpack-plugin@"7.0.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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2025-01-14T09_18_15_833Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-14T09_18_15_833Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

security fix Security fix generated by Mend

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants