tfelder-deloitte / SecurityTesting

Other
0 stars 0 forks source link

Update dependency flickity to v3 #584

Open renovate[bot] opened 2 years ago

renovate[bot] commented 2 years ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
flickity (source) 2.2.2 -> 3.0.0 age adoption passing confidence

Release Notes

metafizzy/flickity ### [`v3.0.0`](https://togithub.com/metafizzy/flickity/compare/v2.3.0...cf2e31bb40096a188de934ce7aeb992366a64d7c) [Compare Source](https://togithub.com/metafizzy/flickity/compare/v2.3.0...cf2e31bb40096a188de934ce7aeb992366a64d7c) ### [`v2.3.0`](https://togithub.com/metafizzy/flickity/releases/tag/v2.3.0): - resolve dragging & scrolling on iOS 15 [Compare Source](https://togithub.com/metafizzy/flickity/compare/v2.2.2...v2.3.0) For [#​1177](https://togithub.com/metafizzy/flickity/issues/1177) 1. I added a check within the browser resize handler to not trigger if animating or dragging. This should help with dragging performance. 2. I switched to Touch Events over Pointer Events, which allow preventDefault so you can disable window scrolling on mobile. This will help with flicking. For [#​1150](https://togithub.com/metafizzy/flickity/issues/1150) - use `transform` or `left/right` positioning for less Cumulative Layout Shift warnings. ### [`v2.2.2`](https://togithub.com/metafizzy/flickity/releases/tag/v2.2.2) [Compare Source](https://togithub.com/metafizzy/flickity/compare/v2.2.1...v2.2.2) - 📦 bump several dependencies for security alerts: [#​1039](https://togithub.com/metafizzy/flickity/issues/1039) [#​1044](https://togithub.com/metafizzy/flickity/issues/1044) [#​1045](https://togithub.com/metafizzy/flickity/issues/1045) [#​1053](https://togithub.com/metafizzy/flickity/issues/1053) [#​1085](https://togithub.com/metafizzy/flickity/issues/1085) - 🥾 Switch from Gulp to npm scripts - 👔 Switch linting from JSHint to ESLint - 🐞 remove aria-hidden on destroy. [#​1005](https://togithub.com/metafizzy/flickity/issues/1005)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.



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

renovate[bot] commented 2 years ago

⚠ 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:

The artifact failure details are included below:

File name: search-parts/package-lock.json
npm notice 
npm notice New minor version of npm available! 8.5.0 -> 8.7.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.7.0>
npm notice Run `npm install -g npm@8.7.0` to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: pnp-modern-search@3.14.2
npm ERR! Found: @types/react@17.0.18
npm ERR! node_modules/@types/react
npm ERR!   dev @types/react@"17.0.18" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @types/react@">=16.8.0 <17.0.0" from @uifabric/file-type-icons@7.6.30
npm ERR! node_modules/@uifabric/file-type-icons
npm ERR!   @uifabric/file-type-icons@"7.6.30" 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-04-25T19_33_26_159Z-debug-0.log
renovate[bot] commented 1 year ago

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.