Skip to content

fix(deps): roll back dependency @xmlking/ngx-knob to ^1.1.1 #936

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 21, 2022

Mend Renovate

This PR contains the following updates:

Package Type Update Change
@​xmlking/ngx-knob dependencies rollback ^1.1.3 -> ^1.1.1

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, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/xmlking-ngx-knob-rollback branch from 8fcbd92 to 51b6d55 Compare January 24, 2022 13:04
@renovate renovate bot force-pushed the renovate/xmlking-ngx-knob-rollback branch from 51b6d55 to 931bdaf Compare June 11, 2022 00:56
@renovate renovate bot changed the title fix(deps): roll back dependency @xmlking/ngx-knob to 1.1.1 fix(deps): roll back dependency @xmlking/ngx-knob to ^1.1.1 Jun 11, 2022
@renovate
Copy link
Author

renovate bot commented Jun 11, 2022

⚠ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @angular/flex-layout@13.0.0-beta.38
npm ERR! Found: @angular/cdk@14.0.1
npm ERR! node_modules/@angular/cdk
npm ERR!   @angular/cdk@"14.0.1" from the root project
npm ERR!   peer @angular/cdk@"14.0.1" from @angular/material@14.0.1
npm ERR!   node_modules/@angular/material
npm ERR!     @angular/material@"14.0.1" from the root project
npm ERR!     peer @angular/material@">=7.0.0" from @ngx-formly/material@5.12.5
npm ERR!     node_modules/@ngx-formly/material
npm ERR!       @ngx-formly/material@"5.12.5" from the root project
npm ERR!     6 more (@ngx-starter-kit/app-confirm, ...)
npm ERR!   6 more (@ngx-starter-kit/app-confirm, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/cdk@"^13.0.0" from @angular/flex-layout@13.0.0-beta.38
npm ERR! node_modules/@angular/flex-layout
npm ERR!   @angular/flex-layout@"13.0.0-beta.38" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @angular/cdk@13.3.9
npm ERR! node_modules/@angular/cdk
npm ERR!   peer @angular/cdk@"^13.0.0" from @angular/flex-layout@13.0.0-beta.38
npm ERR!   node_modules/@angular/flex-layout
npm ERR!     @angular/flex-layout@"13.0.0-beta.38" 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! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-06-11T00_56_17_596Z-debug-0.log

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant