Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 3, 2025

This PR contains the following updates:

Package Type Update Change Age Confidence
@angular-devkit/build-angular devDependencies pin ^20.3.8 -> 20.3.12 age confidence
@angular-eslint/builder (source) devDependencies pin ^20.5.0 -> 20.7.0 age confidence
@angular-eslint/eslint-plugin (source) devDependencies pin ^20.5.0 -> 20.7.0 age confidence
@angular-eslint/eslint-plugin-template (source) devDependencies pin ^20.5.0 -> 20.7.0 age confidence
@angular-eslint/schematics (source) devDependencies pin ^20.5.0 -> 20.7.0 age confidence
@angular-eslint/template-parser (source) devDependencies pin ^20.5.0 -> 20.7.0 age confidence
@angular/cli devDependencies pin ^20.3.8 -> 20.3.12 age confidence
@angular/compiler-cli (source) devDependencies pin ^20.3.9 -> 20.3.14 age confidence
@angular/elements (source) devDependencies pin ^20.3.9 -> 20.3.14 age confidence
@angular/localize devDependencies pin ^20.3.9 -> 20.3.14 age confidence
ng-packagr devDependencies patch 20.3.0 -> 20.3.2 age confidence
ts-jest (source) devDependencies patch 29.4.5 -> 29.4.6 age confidence
zone.js (source, changelog) devDependencies pin ^0.15.1 -> 0.15.1 age confidence

Add the preset :preserveSemverRanges to your config if you don't want to pin your dependencies.


Release Notes

ng-packagr/ng-packagr (ng-packagr)

v20.3.2

Compare Source

Bug Fixes
  • ensure deterministic ordering of 'exports' field (952ca64), closes #​3175

v20.3.1

Compare Source

Performance
  • reduce memory usage for multiple entry-points (non-watch) (e063368), closes #​3168
kulshekhar/ts-jest (ts-jest)

v29.4.6

Compare Source

Bug Fixes

Configuration

📅 Schedule: 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 is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 force-pushed the renovate/fundamental-ngx-and-angular branch 7 times, most recently from 050f149 to 3303341 Compare November 5, 2025 17:45
@renovate renovate bot changed the title Update Fundamental NGX and Angular to v20.5.1 Update Fundamental NGX and Angular Nov 5, 2025
@renovate renovate bot force-pushed the renovate/fundamental-ngx-and-angular branch 22 times, most recently from 9104d43 to f7943fb Compare November 12, 2025 20:10
@renovate renovate bot force-pushed the renovate/fundamental-ngx-and-angular branch 10 times, most recently from 85dcbe8 to 94ae567 Compare December 1, 2025 14:07
@renovate renovate bot changed the title Update Fundamental NGX and Angular Pin dependencies Dec 1, 2025
@renovate renovate bot force-pushed the renovate/fundamental-ngx-and-angular branch 8 times, most recently from c6f3494 to 81eaaad Compare December 3, 2025 15:24
@renovate renovate bot force-pushed the renovate/fundamental-ngx-and-angular branch from 81eaaad to 3a80548 Compare December 8, 2025 20:14
@renovate
Copy link
Contributor Author

renovate bot commented Dec 8, 2025

⚠️ 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 could not resolve
npm error
npm error While resolving: @openmfp/[email protected]
npm error Found: @angular/[email protected]
npm error node_modules/@angular/core
npm error   peer @angular/core@"^19.2.16 || ^20.3.14" from the root project
npm error   peer @angular/core@"^20.0.0" from @angular-builders/[email protected]
npm error   node_modules/@angular-builders/jest
npm error     dev @angular-builders/jest@"20.0.0" from the root project
npm error   11 more (@angular/build, @angular/common, @angular/forms, ...)
npm error
npm error Could not resolve dependency:
npm error dev @angular-devkit/build-angular@"20.3.12" from the root project
npm error
npm error Conflicting peer dependency: @angular/[email protected]
npm error node_modules/@angular/core
npm error   peer @angular/core@"20.3.15" from @angular/[email protected]
npm error   node_modules/@angular/service-worker
npm error     peerOptional @angular/service-worker@"^20.0.0" from @angular-devkit/[email protected]
npm error     node_modules/@angular-devkit/build-angular
npm error       dev @angular-devkit/build-angular@"20.3.12" 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-12-16T15_22_40_754Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-12-16T15_22_40_754Z-debug-0.log

@renovate renovate bot force-pushed the renovate/fundamental-ngx-and-angular branch 6 times, most recently from 691ef3c to 83b21e7 Compare December 15, 2025 17:35
@renovate renovate bot force-pushed the renovate/fundamental-ngx-and-angular branch from 83b21e7 to 5782101 Compare December 16, 2025 15:20
@renovate renovate bot force-pushed the renovate/fundamental-ngx-and-angular branch from 5782101 to 76e0d04 Compare December 16, 2025 15:22
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.

1 participant