chore(deps): update dependency date-fns-tz to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
date-fns-tz	^2.0.0 -> ^3.0.0

---

Release Notes

marnusw/date-fns-tz (date-fns-tz)

v3.2.0

Compare Source

• [DEPS] [email protected] supported (#​301)
• [PERFORMANCE] Make testDateFormatted static to avoid re-initialising it on every call (#​297) @​hurali97
• [ENHANCEMENT] Compatibility with date-fns setDefaultOptions (#​286) @​yangchristina
• [DOCS] Fixed table of contents links (#​284)

v3.1.3

Compare Source

• [BUGFIX] Make getTimeZoneOffset's 2nd arg optional

v3.1.2

Compare Source

• [BUGFIX] Fix formatInTimeZone use of timeZone string (#​280)

v3.1.1

Compare Source

• [BUGFIX] getTimeZoneOffset's 2nd arg should be optional (#​281)

v3.1.0

Compare Source

• [REFACTOR] Full rewrite in TypeScript (#​278) Thank you, @​brettwillis
• [BREAKING CHANGE] OptionsWithTZ is now either FormatOptionsWithTZ or ToDateOptionsWithTZ, matching date-fns

v3.0.1

Compare Source

• [BUGFIX] Fix named export typings (#​277)

v3.0.0

Compare Source

• [UPGRADE] Support date-fns v3 (#​265) Thank you, @​christopherklint97
• [BUGFIX] Correct import of date-fns@v3 format and use Babel Webpack loader for mjs files (#​271)
• [BREAKING CHANGE] date-fns v2 is no longer supported
• [BREAKING CHANGE] Renamed utcToZonedTime to toZonedTime to make the name less confusing, just search & replace
• [BREAKING CHANGE] Renamed zonedTimeToUtc to fromZonedTime to make the name less confusing, just search & replace
• [BREAKING CHANGE] All functions are now exported using named exports, this requires changing direct
  imports from import formatInTimeZone from 'date-fns-tz/formatInTimeZone' to
  import { formatInTimeZone } from 'date-fns-tz/formatInTimeZone'
• [BREAKING CHANGE] Functions now don’t check the number of passed arguments, delegating this task to type checkers
  (This isn't fully implemented yet, but it should be the assumption moving forward, as it is in date-fns)
• [BREAKING CHANGE] Arguments are not explicitly converted to the target types. Instead, they are passed as is,
  delegating this task to type checkers (This isn't fully implemented yet, but it should be the assumption
  moving forward, as it is in date-fns)
• [BREAKING CHANGE] IE is no longer supported since date-fns no longer supports it
• [BREAKING CHANGE] Removed flow support since date-fns also removed it

---

Configuration

📅 Schedule: Branch creation - "after 7pm every weekday,before 5am every weekday" in timezone Europe/Madrid, 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.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
unleash-docs	⬜️ Ignored (Inspect)	Visit Preview		Apr 1, 2025 9:30am

[github-actions]

Dependency Review

The following issues were found:

• ✅ 0 vulnerable package(s)
• ✅ 0 package(s) with incompatible licenses
• ✅ 0 package(s) with invalid SPDX license definitions
• ✅ 0 package(s) with unknown licenses.
• ⚠️ 2 packages with OpenSSF Scorecard issues.

See the Details below.

OpenSSF Scorecard

Package	Version	Score	Details
npm/date-fns-tz	^3.0.0	⚠️ 2.9	Details Check Score Reason Dangerous-Workflow ⚠️ -1 no workflows found Maintained ⚠️ 1 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1 Code-Review 🟢 5 Found 9/16 approved changesets -- score normalized to 5 Token-Permissions ⚠️ -1 No tokens found Packaging ⚠️ -1 packaging workflow not detected Binary-Artifacts 🟢 10 no binaries found in the repo CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Pinned-Dependencies ⚠️ -1 no dependencies found Security-Policy ⚠️ 0 security policy file not detected License 🟢 10 license file detected Fuzzing ⚠️ 0 project is not fuzzed Signed-Releases ⚠️ -1 no releases found Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0 Vulnerabilities ⚠️ 0 13 existing vulnerabilities detected
npm/date-fns-tz	3.2.0	⚠️ 2.9	Details Check Score Reason Dangerous-Workflow ⚠️ -1 no workflows found Maintained ⚠️ 1 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1 Code-Review 🟢 5 Found 9/16 approved changesets -- score normalized to 5 Token-Permissions ⚠️ -1 No tokens found Packaging ⚠️ -1 packaging workflow not detected Binary-Artifacts 🟢 10 no binaries found in the repo CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Pinned-Dependencies ⚠️ -1 no dependencies found Security-Policy ⚠️ 0 security policy file not detected License 🟢 10 license file detected Fuzzing ⚠️ 0 project is not fuzzed Signed-Releases ⚠️ -1 no releases found Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0 Vulnerabilities ⚠️ 0 13 existing vulnerabilities detected

Scanned Files

• frontend/package.json
• frontend/yarn.lock