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

Update dependency flickity to v3 #584

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 5, 2022

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

Compare Source

v2.3.0: - resolve dragging & scrolling on iOS 15

Compare Source

For #​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 - use transform or left/right positioning for less Cumulative Layout Shift warnings.

v2.2.2

Compare Source


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.


  • If you want to rebase/retry this PR, check this box

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

@renovate
Copy link
Contributor Author

renovate bot commented Mar 5, 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: 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 renovate bot force-pushed the renovate/flickity-3.x branch 2 times, most recently from c0e132a to 1a1d178 Compare March 12, 2022 03:10
@renovate renovate bot force-pushed the renovate/flickity-3.x branch from 1a1d178 to 6f36bf1 Compare March 15, 2022 01:24
@renovate renovate bot force-pushed the renovate/flickity-3.x branch from 6f36bf1 to b94816a Compare April 25, 2022 19:33
@renovate
Copy link
Contributor Author

renovate bot commented Mar 23, 2023

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant