Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency copy-webpack-plugin to v10 #277

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 10, 2022

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
copy-webpack-plugin 6.4.1 -> 10.2.4 age adoption passing confidence

Release Notes

webpack-contrib/copy-webpack-plugin

v10.2.4

Compare Source

v10.2.3

Compare Source

v10.2.2

Compare Source

v10.2.1

Compare Source

v10.2.0

Compare Source

Features
  • removed cjs wrapper and generated types in commonjs format (export = and namespaces used in types), now you can directly use exported types (#​654) (5901006)

v10.1.0

Compare Source

Features
Bug Fixes

v10.0.0

Compare Source

⚠ BREAKING CHANGES
  • minimum supported Node.js version is 12.20.0
  • update globby to 12.0.2 version

v9.1.0

Compare Source

Features
Bug Fixes
  • compatibility with Node.js 17 (20af0c7)
9.0.1 (2021-06-25)
Chore
  • update serialize-javascript

v9.0.1

Compare Source

v9.0.0

Compare Source

⚠ BREAKING CHANGES
  • minimum supported Node.js version is 12.13.0
8.1.1 (2021-04-06)
Bug Fixes

v8.1.1

Compare Source

v8.1.0

Compare Source

Features

v8.0.0

Compare Source

⚠ BREAKING CHANGES
  • logic for some placeholders was changed:
    • [hash] and [fullhash] works as in webpack (i.e. it is hash of build, not content hash of file), to migrate change [name].[hash].[ext] to [name].[contenthash][ext]
    • [ext] doesn't require . (dot) before, i.e. change [name].[ext] to [name][ext]
    • [<hashType>:contenthash:<digestType>:<length>] and [<hashType>:hash:<digestType>:<length>] is not supported anymore, you can use output.hashDigest, output.hashDigestLength and output.hashFunction options to setup it
    • [N] was removed in favor of using the to option as a function
    • [folder] was removed
    • [emoji] was removed
Features

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

Configuration

📅 Schedule: 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 WhiteSource Renovate. View repository job log here.

@renovate
Copy link
Author

renovate bot commented Feb 10, 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 notice 
npm notice New minor version of npm available! 8.3.1 -> 8.5.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.5.0>
npm notice Run `npm install -g [email protected]` to update!
npm notice 
npm WARN using --force Recommended protections disabled.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/webpack
npm ERR!   dev webpack@"4.46.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^5.1.0" from [email protected]
npm ERR! node_modules/copy-webpack-plugin
npm ERR!   dev copy-webpack-plugin@"10.2.4" 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-10T23_14_37_571Z-debug-0.log

@stormkit-io
Copy link

stormkit-io bot commented Feb 10, 2022

Deployment failed

This pull request failed while building automatically on Stormkit. You can preview the logs using the following link.

https://app.stormkit.io/app/1644802351/deployments/53199487240744

@eldemcan eldemcan closed this Feb 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants