Skip to content

Update dependency react-day-picker to v8.10.2#40

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/react-day-picker-8.x
Open

Update dependency react-day-picker to v8.10.2#40
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/react-day-picker-8.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 6, 2026

This PR contains the following updates:

Package Change Age Confidence
react-day-picker (source) 8.10.18.10.2 age confidence

Release Notes

gpbl/react-day-picker (react-day-picker)

v8.10.2

Compare Source

Expands the React peer dependency to include React 19, helping projects that are still on DayPicker v8 adopt newer React versions without peer dependency warnings.

Upgrading to v9

Please not that DayPicker v8 is in maintenance mode. This release helps existing v8 users stay unblocked, but upgrading to v9 is recommended when possible. If you are still on v8, review the updated upgrade guide: https://daypicker.dev/upgrading

What's Changed

Full Changelog: gpbl/react-day-picker@v8.10.1...v8.10.2


Configuration

📅 Schedule: (in timezone Asia/Jerusalem)

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

@renovate renovate Bot added the renovate label May 6, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 6, 2026

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/date-fns
npm error   date-fns@"4.1.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer date-fns@"^2.28.0 || ^3.0.0" from [email protected]
npm error node_modules/react-day-picker
npm error   react-day-picker@"8.10.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps 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/2026-05-18T13_53_30_153Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-05-18T13_53_30_153Z-debug-0.log

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 6, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
10x-crm Ready Ready Preview, Comment May 18, 2026 1:54pm

Request Review

Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 2 files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants