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(deps)!: Update dependency ng-packagr to v19 #693

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

marcolongol-bot[bot]
Copy link
Contributor

@marcolongol-bot marcolongol-bot bot commented Nov 21, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ng-packagr ~18.2.0 -> ~19.1.0 age adoption passing confidence

Warning

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


Release Notes

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

v19.1.1

Compare Source

v19.1.0

Compare Source

Features
Bug Fixes
  • Re-use module resolution cache.
  • adjust peerDependencies to allow Angular 19.1.0-next (d27ef5b)
Performance
  • mitigate TypeScript 5.6+ performance regression (ac9766e), closes #​2969

v19.0.1

Compare Source

v19.0.0

Compare Source

Features
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 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 Renovate Bot.

Copy link
Contributor Author

marcolongol-bot bot commented Nov 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: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @marcolongo.cloud/[email protected]
npm error Found: @angular/[email protected]
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 || ^19.1.0-next.0 || ^19.2.0-next.0" from [email protected]
npm error node_modules/ng-packagr
npm error   dev ng-packagr@"~19.1.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/2025-01-28T16_53_15_225Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-28T16_53_15_225Z-debug-0.log

@marcolongol-bot marcolongol-bot bot force-pushed the renovate/ng-packagr-19.x branch 4 times, most recently from 04d8f24 to 2d97ef6 Compare November 29, 2024 01:36
@marcolongol-bot marcolongol-bot bot force-pushed the renovate/ng-packagr-19.x branch 2 times, most recently from 20935bf to df3d2d1 Compare January 16, 2025 05:09
@marcolongol-bot marcolongol-bot bot force-pushed the renovate/ng-packagr-19.x branch 3 times, most recently from f5fac00 to 4d5fcc0 Compare January 28, 2025 03:52
marcolongol and others added 2 commits January 28, 2025 08:48
Signed-off-by: marcolongol-bot <166586793+marcolongol-bot[bot]@users.noreply.github.com>
@marcolongol-bot marcolongol-bot bot force-pushed the renovate/ng-packagr-19.x branch from 4d5fcc0 to 08fa06a Compare January 28, 2025 16:53
@marcolongol-bot marcolongol-bot bot changed the base branch from main to develop January 28, 2025 16:53
Copy link
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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.

1 participant