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

Update dependency babel-loader to v8.4.1 #93

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 1, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
babel-loader 8.2.5 -> 8.4.1 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

babel/babel-loader (babel-loader)

v8.4.1

Compare Source

v8.4.0

Compare Source

v8.3.0

Compare Source

New features

Full Changelog: babel/babel-loader@v8.2.5...v8.3.0


Configuration

📅 Schedule: Branch creation - "before 7am on the first day of the month" in timezone Europe/Helsinki, 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.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Aug 1, 2023

⚠ 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: hugo/themes/ananke/src/package-lock.json
/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: assets-webpack-plugin@7.0.0
npm ERR! Found: webpack@4.0.1
npm ERR! node_modules/webpack
npm ERR!   dev webpack@"4.0.1" from the root project
npm ERR!   peer webpack@"^4.0.0 || ^5.0.0" from file-loader@6.2.0
npm ERR!   node_modules/file-loader
npm ERR!     dev file-loader@"6.2.0" from the root project
npm ERR!   2 more (uglifyjs-webpack-plugin, babel-loader)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@">=5.0.0" from assets-webpack-plugin@7.0.0
npm ERR! node_modules/assets-webpack-plugin
npm ERR!   dev assets-webpack-plugin@"7.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: webpack@5.88.2
npm ERR! node_modules/webpack
npm ERR!   peer webpack@">=5.0.0" from assets-webpack-plugin@7.0.0
npm ERR!   node_modules/assets-webpack-plugin
npm ERR!     dev assets-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/worker/bc0837/1c21ef/cache/others/npm/_logs/2023-08-01T03_38_09_621Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/bc0837/1c21ef/cache/others/npm/_logs/2023-08-01T03_38_09_621Z-debug-0.log

@renovate renovate bot changed the title Update dependency babel-loader to v8.3.0 Update dependency babel-loader to v8.4.0 Sep 21, 2024
Copy link
Contributor Author

renovate bot commented Sep 21, 2024

⚠️ 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: hugo/themes/ananke/src/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: assets-webpack-plugin@7.0.0
npm error Found: webpack@4.0.1
npm error node_modules/webpack
npm error   dev webpack@"4.0.1" from the root project
npm error   peer webpack@"^4.0.0 || ^5.0.0" from file-loader@6.2.0
npm error   node_modules/file-loader
npm error     dev file-loader@"6.2.0" from the root project
npm error   2 more (uglifyjs-webpack-plugin, babel-loader)
npm error
npm error Could not resolve dependency:
npm error peer webpack@">=5.0.0" from assets-webpack-plugin@7.0.0
npm error node_modules/assets-webpack-plugin
npm error   dev assets-webpack-plugin@"7.0.0" from the root project
npm error
npm error Conflicting peer dependency: webpack@5.94.0
npm error node_modules/webpack
npm error   peer webpack@">=5.0.0" from assets-webpack-plugin@7.0.0
npm error   node_modules/assets-webpack-plugin
npm error     dev assets-webpack-plugin@"7.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-09-21T17_07_17_597Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-09-21T17_07_17_597Z-debug-0.log

@renovate renovate bot changed the title Update dependency babel-loader to v8.4.0 Update dependency babel-loader to v8.4.1 Sep 21, 2024
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