Skip to content

chore(deps): update dependency @angular-builders/custom-webpack to v19 - autoclosed#464

Closed
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/angular-builders-custom-webpack-19.x
Closed

chore(deps): update dependency @angular-builders/custom-webpack to v19 - autoclosed#464
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/angular-builders-custom-webpack-19.x

Conversation

@renovate

@renovate renovate Bot commented Jan 8, 2025

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@angular-builders/custom-webpack (source) ^18 -> ^19.0.0 age adoption passing confidence

Release Notes

just-jeb/angular-builders (@​angular-builders/custom-webpack)

v19.0.0

Compare Source

Note: Version bump only for package @​angular-builders/custom-webpack


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 renovate Bot added the chore(deps) label Jan 8, 2025
@renovate

renovate Bot commented Jan 8, 2025

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: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: rbtech@1.0.0
npm error Found: @angular/compiler-cli@18.2.0
npm error node_modules/@angular/compiler-cli
npm error   dev @angular/compiler-cli@"18.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @angular/compiler-cli@"^19.0.0" from @angular-builders/custom-webpack@19.0.1
npm error node_modules/@angular-builders/custom-webpack
npm error   dev @angular-builders/custom-webpack@"^19.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 /runner/cache/others/npm/_logs/2025-06-22T21_52_46_115Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-06-22T21_52_46_115Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/angular-builders-custom-webpack-19.x branch 4 times, most recently from 2f1e19b to 3e07c6f Compare January 11, 2025 02:09
@renovate
renovate Bot force-pushed the renovate/angular-builders-custom-webpack-19.x branch from 3e07c6f to 2d4b01a Compare May 28, 2025 19:06
@renovate
renovate Bot force-pushed the renovate/angular-builders-custom-webpack-19.x branch 18 times, most recently from 7ec9669 to fab3dd0 Compare June 22, 2025 17:29
@renovate
renovate Bot force-pushed the renovate/angular-builders-custom-webpack-19.x branch from fab3dd0 to 47d5741 Compare June 22, 2025 21:52
@renovate renovate Bot changed the title chore(deps): update dependency @angular-builders/custom-webpack to v19 chore(deps): update dependency @angular-builders/custom-webpack to v19 - autoclosed Jun 25, 2025
@renovate renovate Bot closed this Jun 25, 2025
@renovate
renovate Bot deleted the renovate/angular-builders-custom-webpack-19.x branch June 25, 2025 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants