feat: support date-fns v4 (#674)

* chore(deps): bump date-fns to v4

* Unlbock CI

* Update lock file

---------

Co-authored-by: Dmitriy Kovalenko <dmtr.kovalenko@outlook.com>

Author: babu-ch

.github/workflows/build.yml

@@ -7,20 +7,12 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/checkout@v2
-      - uses: actions/setup-node@v2
+      - uses: actions/checkout@v4
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
         with:
-          node-version: "18"
-      - name: Get yarn cache directory path
-        id: yarn-cache-dir-path
-        run: echo "::set-output name=dir::$(yarn config get cacheFolder)"
-      - uses: actions/cache@v2
-        id: yarn-cache
-        with:
-          path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
-          key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
-          restore-keys: |
-            ${{ runner.os }}-yarn-
+          node-version: 23
+          cache: "yarn"
 
       - name: Install
         run: yarn install --frozen-lockfile

README.md

@@ -9,7 +9,7 @@ Abstraction over common JavaScript date management libraries.
 [![lerna](https://img.shields.io/badge/maintained%20with-lerna-cc00ff.svg)](https://lerna.js.org/)
 [![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)
 
-The project exposes an abstraction interface over [luxon](https://moment.github.io/luxon/), [date-fns v3](https://github.com/date-fns/date-fns), [dayjs](https://github.com/iamkun/dayjs) and [moment](https://momentjs.com/).
+The project exposes an abstraction interface over [luxon](https://moment.github.io/luxon/), [date-fns v4](https://github.com/date-fns/date-fns), [dayjs](https://github.com/iamkun/dayjs) and [moment](https://momentjs.com/).
 It allows you to build any UI date or time components while utilizing the same date management library in use within your user's project.
 
 It simplifies timezone management, allows your code to return the exact same type that your user expects and works with specific calendar systems (e.g. [Jalali calendar](https://en.wikipedia.org/wiki/Jalali_calendar))

packages/date-fns/package.json

@@ -30,7 +30,7 @@
   },
   "license": "MIT",
   "peerDependencies": {
-    "date-fns": "^3.2.0"
+    "date-fns": "^3.2.0 || ^4.1.0"
   },
   "peerDependenciesMeta": {
     "date-fns": {
@@ -41,7 +41,7 @@
     "@date-io/core": "^3.2.0"
   },
   "devDependencies": {
-    "date-fns": "^3.2.0",
+    "date-fns": "^4.1.0",
     "rollup": "^2.0.2",
     "typescript": "^5.0.0"
   },