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 propagating-hammerjs to v3 - autoclosed #498

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 4, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
propagating-hammerjs ^1.4.0 -> ^3.0.0 age adoption passing confidence

Release Notes

josdejong/propagating-hammerjs (propagating-hammerjs)

v3.0.0

Compare Source

  • Breaking: Dropped support for IE 11
  • Fix: Use event.target in cases where the target has been removed
    from the DOM (#​17). Thanks @​sgparrish.

v2.0.1

Compare Source

  • Fix broken urls to hammerjs in examples.

v2.0.0

Compare Source

  • Switched from hammerjs to @egjs/hammerjs because the former is not
    actively maintained. Thanks @​mojoaxel.
  • Change from having hammemrjs as dependency of this library to having it
    as peerDependency. Thanks @​mojoaxel.

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.

🔕 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.

Copy link
Contributor Author

renovate bot commented Apr 4, 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/propagating-hammerjs
npm ERR!   dev propagating-hammerjs@"^3.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer propagating-hammerjs@"^1.4.0 || ^2.0.0" from [email protected]
npm ERR! node_modules/vis-timeline
npm ERR!   vis-timeline@"~7.7.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/propagating-hammerjs
npm ERR!   peer propagating-hammerjs@"^1.4.0 || ^2.0.0" from [email protected]
npm ERR!   node_modules/vis-timeline
npm ERR!     vis-timeline@"~7.7.0" 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-04-04T08_12_35_071Z-eresolve-report.txt

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

@renovate renovate bot force-pushed the renovate/propagating-hammerjs-3.x branch 4 times, most recently from 4ceb1f4 to ebc24a9 Compare April 4, 2024 08:12
Copy link
Contributor Author

renovate bot commented Jun 6, 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 could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/propagating-hammerjs
npm error   dev propagating-hammerjs@"^3.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer propagating-hammerjs@"^1.4.0 || ^2.0.0" from [email protected]
npm error node_modules/vis-timeline
npm error   vis-timeline@"~7.7.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/propagating-hammerjs
npm error   peer propagating-hammerjs@"^1.4.0 || ^2.0.0" from [email protected]
npm error   node_modules/vis-timeline
npm error     vis-timeline@"~7.7.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/2024-07-09T04_03_05_150Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-07-09T04_03_05_150Z-debug-0.log

@renovate renovate bot force-pushed the renovate/propagating-hammerjs-3.x branch 4 times, most recently from 4e30be6 to 8e9f2a5 Compare June 11, 2024 15:32
@renovate renovate bot force-pushed the renovate/propagating-hammerjs-3.x branch 6 times, most recently from 6964fee to d5a438b Compare June 22, 2024 10:40
@renovate renovate bot force-pushed the renovate/propagating-hammerjs-3.x branch from d5a438b to 711fabd Compare June 26, 2024 01:13
@renovate renovate bot force-pushed the renovate/propagating-hammerjs-3.x branch 4 times, most recently from 29d46b2 to 7970be2 Compare July 8, 2024 18:03
@renovate renovate bot force-pushed the renovate/propagating-hammerjs-3.x branch from 7970be2 to c617160 Compare July 9, 2024 04:03
@renovate renovate bot changed the title chore(deps): update dependency propagating-hammerjs to v3 chore(deps): update dependency propagating-hammerjs to v3 - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/propagating-hammerjs-3.x branch December 8, 2024 18:54
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.

0 participants