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(e2e/a18): update dependency ng-packagr to v18.0.0 #8793

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 18, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ng-packagr 18.0.0-next.1 -> 18.0.0 age adoption passing confidence

Release Notes

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

v18.0.0

Compare Source

⚠ BREAKING CHANGES
  • Node.js support for versions <18.19.1 and <20.11.1 has been removed.
Bug Fixes
  • incorrect path resolution for entry-points when generating FESM (f2cd914), closes #​2838
Features
  • add support for Angular 18 (9bef232)
  • add NgPackagrOptions to public api (ffc512e)
  • add support for polling (2c7f75b)
  • support TypeScript 5.4 (07d5cea)

v18.0.0-rc.0

Compare Source

v18.0.0-next.4

Compare Source

Bug Fixes
  • incorrect path resolution for entry-points when generating FESM (f2cd914), closes #​2838

v18.0.0-next.3

Compare Source

Bug Fixes
  • add NgPackagrOptions to public api (ffc512e)

v18.0.0-next.2

Compare Source

Features
  • add support for polling (2c7f75b)

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 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 has been generated by Mend Renovate. View repository job log here.

Copy link
Contributor Author

renovate bot commented Apr 18, 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: e2e/a18/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: jest-preset-angular@14.0.3
npm ERR! Found: @angular-devkit/build-angular@18.0.0-next.2
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR!   dev @angular-devkit/build-angular@"18.0.0-next.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular-devkit/build-angular@">=15.0.0 <18.0.0" from jest-preset-angular@14.0.3
npm ERR! node_modules/jest-preset-angular
npm ERR!   dev jest-preset-angular@"14.0.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @angular-devkit/build-angular@17.3.6
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR!   peer @angular-devkit/build-angular@">=15.0.0 <18.0.0" from jest-preset-angular@14.0.3
npm ERR!   node_modules/jest-preset-angular
npm ERR!     dev jest-preset-angular@"14.0.3" 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/renovate/cache/others/npm/_logs/2024-05-02T09_11_14_581Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-02T09_11_14_581Z-debug-0.log

Copy link

codecov bot commented Apr 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (0dd01fe) to head (983a51c).

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #8793   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          227       227           
  Lines         4935      4935           
  Branches      1147      1147           
=========================================
  Hits          4935      4935           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/e2e/a18/ng-packagr-18.0.x branch from 5f211af to 0baf381 Compare April 26, 2024 06:03
@renovate renovate bot changed the title chore(e2e/a18): update dependency ng-packagr to v18.0.0-next.3 chore(e2e/a18): update dependency ng-packagr to v18.0.0-next.4 Apr 26, 2024
@renovate renovate bot force-pushed the renovate/e2e/a18/ng-packagr-18.0.x branch from 0baf381 to 6b58e33 Compare May 2, 2024 09:11
@renovate renovate bot changed the title chore(e2e/a18): update dependency ng-packagr to v18.0.0-next.4 chore(e2e/a18): update dependency ng-packagr to v18.0.0-rc.0 May 2, 2024
@renovate renovate bot force-pushed the renovate/e2e/a18/ng-packagr-18.0.x branch from 6b58e33 to 983a51c Compare May 22, 2024 17:00
@renovate renovate bot changed the title chore(e2e/a18): update dependency ng-packagr to v18.0.0-rc.0 chore(e2e/a18): update dependency ng-packagr to v18.0.0 May 22, 2024
Copy link
Contributor Author

renovate bot commented May 22, 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: e2e/a18/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: jest-preset-angular@14.0.3
npm ERR! Found: @angular-devkit/build-angular@18.0.0-next.2
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR!   dev @angular-devkit/build-angular@"18.0.0-next.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular-devkit/build-angular@">=15.0.0 <18.0.0" from jest-preset-angular@14.0.3
npm ERR! node_modules/jest-preset-angular
npm ERR!   dev jest-preset-angular@"14.0.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @angular-devkit/build-angular@17.3.7
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR!   peer @angular-devkit/build-angular@">=15.0.0 <18.0.0" from jest-preset-angular@14.0.3
npm ERR!   node_modules/jest-preset-angular
npm ERR!     dev jest-preset-angular@"14.0.3" 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/renovate/cache/others/npm/_logs/2024-05-22T17_00_29_683Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-22T17_00_29_683Z-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.

None yet

0 participants