Skip to content

Update dependency grunt-webpack to v8#167

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/grunt-webpack-8.x
Open

Update dependency grunt-webpack to v8#167
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/grunt-webpack-8.x

Conversation

@renovate

@renovate renovate Bot commented May 24, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
grunt-webpack ^7.0.0^8.0.0 age confidence

Release Notes

danez/grunt-webpack (grunt-webpack)

v8.0.0

Compare Source

Features
  • Drop support for Node.js 18, 19, 20, 21 (32f269a)
BREAKING CHANGES
  • Minimum supported Node.js version is now 22.13.0

v7.0.1

Compare Source

Bug Fixes
  • Call compiler.close() so webpack writes cache to disk (#​252) (cb78db9)

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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 was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented May 24, 2026

Copy link
Copy Markdown
Contributor 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: krew.io-source/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: closure-webpack-plugin@2.6.1
npm ERR! Found: webpack@5.94.0
npm ERR! node_modules/webpack
npm ERR!   webpack@"^5.94.0" from the root project
npm ERR!   peer webpack@"^5.1.0" from terser-webpack-plugin@5.3.10
npm ERR!   node_modules/terser-webpack-plugin
npm ERR!     terser-webpack-plugin@"^5.3.10" from webpack@5.94.0
npm ERR!   1 more (grunt-webpack)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"4.x" from closure-webpack-plugin@2.6.1
npm ERR! node_modules/closure-webpack-plugin
npm ERR!   closure-webpack-plugin@"^2.5.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: webpack@4.47.0
npm ERR! node_modules/webpack
npm ERR!   peer webpack@"4.x" from closure-webpack-plugin@2.6.1
npm ERR!   node_modules/closure-webpack-plugin
npm ERR!     closure-webpack-plugin@"^2.5.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 /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-06-11T13_08_04_434Z-debug-0.log

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.

0 participants