Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 16, 2024

This PR contains the following updates:

Package Change Age Confidence
flickity-fade ^1.0.0 -> ^2.0.0 age confidence

Release Notes

metafizzy/flickity-fade (flickity-fade)

v2.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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 was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Dec 16, 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: site/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm warn Unknown project config "enable-pre-post-scripts". This will stop working in the next major version of npm.
npm warn Unknown project config "auto-install-peers". This will stop working in the next major version of npm.
npm warn Unknown project config "node-linker". This will stop working in the next major version of npm.
npm warn Unknown project config "prefer-symlinked-executables". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: acend-website@0.0.0
npm error Found: flickity@2.3.0
npm error node_modules/flickity
npm error   flickity@"^2.3.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer flickity@"^3.0.0" from flickity-fade@2.0.0
npm error node_modules/flickity-fade
npm error   flickity-fade@"^2.0.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 /runner/cache/others/npm/_logs/2025-12-03T19_38_58_243Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-12-03T19_38_58_243Z-debug-0.log

@renovate renovate bot force-pushed the renovate/flickity-fade-2.x branch from 97be9b1 to 919e667 Compare August 10, 2025 14:23
@renovate renovate bot force-pushed the renovate/flickity-fade-2.x branch from 919e667 to 2a976bf Compare September 25, 2025 18:51
@renovate renovate bot force-pushed the renovate/flickity-fade-2.x branch from 2a976bf to 940838d Compare November 11, 2025 01:02
@renovate renovate bot changed the title Update dependency flickity-fade to v2 fix(deps): update dependency flickity-fade to v2 Nov 19, 2025
@renovate renovate bot force-pushed the renovate/flickity-fade-2.x branch from 940838d to bf106a7 Compare December 3, 2025 19:39
@netlify
Copy link

netlify bot commented Dec 3, 2025

Deploy Preview for acend-website-new failed.

Name Link
🔨 Latest commit bf106a7
🔍 Latest deploy log https://app.netlify.com/projects/acend-website-new/deploys/693091d71ab0040009d9cc6f

@renovate renovate bot changed the title fix(deps): update dependency flickity-fade to v2 Update dependency flickity-fade to v2 Dec 11, 2025
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