feat(deps)!: Update dependency date-fns (2.30.0 → 4.4.0) by its-miso[bot] · Pull Request #185 · misospace/KubeTix

its-miso · 2026-07-02T04:42:24Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
date-fns	`^2.30.0` → `^4.0.0`

Release Notes

date-fns/date-fns (date-fns)

`v4.4.0`

Compare Source

This release revisits the approach to CDN usage and introduces a new package, @date-fns/cdn and deprecates the date-fns CDN scripts. It allowed reducing the zipped package size from 5.83 MB down to 3.96 MB without introducing any breaking changes.

In v5.0.0-alpha.0 where CDN scripts are completely removed from date-fns the change is more significant and brings the zipped package size down to 2.89 MB.

It is just the first step in optimizing the package size. Expect further size reduction in the future v4 and v5 versions.

Changed

DEPRECATED: The date-fns CDN scripts are now deprecated and will be removed in the next major release. Please switch to the new @date-fns/cdn package for CDN usage.
Removed CDN source maps to reduce the package size. If you rely on them, please switch to the new @date-fns/cdn package that still includes them.

`v4.3.0`

Compare Source

Kudos to @ImRodry and @puneetdixit200 for their contributions.

Fixed

Fixed missing modularized optimization fallback (for Next.js and others). See #4193.
Fixed pt locale first day of week to be Sunday. See #4195 by @ImRodry.
Fixed zh-CN, zh-HK, and zh-TW locale month parsing for October, November, and December. See #4194 by @puneetdixit200.

`v4.2.1`

Compare Source

Fixed

Fixed type definitions missing in v4.2.0 due to TypeScript misconfiguration.

`v4.2.0`

Compare Source

This is a minor release in all senses, it only includes documentation updates (first of many) that points to the new You Don't Need date-fns* page.

* Not really

Changed

Added Temporal API references to the JSDoc annotations of add, addBusinessDays, and addDays.

`v4.1.0`

Compare Source

This release adds time zone support to format functions (that I somehow missed when working on the feature) and fixes a few bugs.

Make sure also upgrade TZDate to v1.0.2 as it includes a bunch of critical bug fixes.

Fixed

Fixed internal constructFrom throwing an exception on null arguments. While null isn't allowed, the functions should rather return Invalid Date or NaN in such cases. See #3885.

Added

Added missing time zone support to format, formatISO, formatISO9075, formatRelative and formatRFC3339. See #3886.

`v4.0.0`

Compare Source

I have great news! First, ten years after its release, date-fns finally gets first-class time zone support.

Another great news is that there aren't many breaking changes in this release. All of them are type-related and will affect only those explicitly using internal date-fns types. Finally, it has been less than a year since the last major release, which is an improvement over the previous four years between v2 and v3. I plan on keeping the pace and minimizing breaking changes moving forward.

Read more about the release in the announcement blog post.

- Sasha @kossnocorp

Added

Added time zones support via @date-fns/tz's TZDate class and tz helper function. See its README for the details about the API.
All relevant functions now accept the context in option, which allows to specify the time zone to make the calculations in. If the function also returns a date, it will be in the specified time zone:
```
import { addDays, startOfDay } from "date-fns";
import { tz } from "@&#8203;date-fns/tz";

startOfDay(addDays(Date.now(), 5, { in: tz("Asia/Singapore") }));
//=> "2024-09-16T00:00:00.000+08:00"
```
In the example, addDays will get the current date and time in Singapore and add 5 days to it. startOfDay will inherit the date type and return the start of the day in Singapore.

Changed

The function arguments, as well as Interval's start and end, now can be of different types, allowing you to mix UTCDate, TZDate, Date, and other extensions, as well as primitives (strings and numbers).

The functions will normalize these values, make calculations, and return the result in the same type, preventing any bugs caused by the discrepancy. If passed, the type will be inferred from the context in option or the first encountered argument object type. The Interval's start and end will be considered separately, starting from start.

In the given example, the result will be in the TZDate as the first argument is a number, and the start takes precedence over the end.
```
clamp(Date.now(), {
  start: new TZDate(start, "Asia/Singapore"),
  end: new UTCDate(),
});
//=> TZDate
```
BREAKING: This release contains a bunch of types changes that should not affect the library's expected usage. The changes are primarily internal and nuanced, so rather than listing them here, I recommend you run the type checker after the upgrade. If there are unfixable problems, please open an issue.
BREAKING: The package is now ESM-first. CommonJS is still supported, and it should not affect most users, but it might break in certain environments. If you encounter any issues, please report them.

Fixed

Fixed CDN build compatibility with jQuery and other tools that expose $ by properly wrapping the code in an IIFE.

`v3.6.0`

Compare Source

On this release worked @kossnocorp and @world1dan. Also, thanks to @seated for sponsoring me.

Fixed

Added

Added the Northern Sámi (se) locale.
Added the constructNow function that creates the current date using the passed reference date's constructor.

`v3.4.0`

Compare Source

Kudos to @kossnocorp, @sakamossan, and @Revan99 for working on the release. Also, thanks to @seated for sponsoring me.

Added

`v3.3.1`

Compare Source

Kudos to @kossnocorp and @fturmel for working on the release.

Fixed

Fixed DST issue in getOverlappingDaysInIntervals, resulting in an inconsistent number of days returned for intervals starting and ending in different DST periods.
Fixed functions incorrectly using trunc instead of round. The bug was introduced in v3.3.0. The affected functions: differenceInCalendarDays, differenceInCalendarISOWeeks, differenceInCalendarWeeks, getISOWeek, getWeek, and getISOWeeksInYear.

`v3.3.0`

Compare Source

On this release worked @kossnocorp, @TheKvikk, @fturmel and @ckcherry23.

Fixed

Fixed the bug in getOverlappingDaysInIntervals caused by incorrect sorting of interval components that led to 0 for timestamps of different lengths.
Fixed bugs when working with negative numbers caused by using Math.floor (-1.1 → -2) instead of Math.trunc (-1.1 → -1). Most of the conversion functions (i.e., hoursToMinutes) were affected when passing some negative fractional input. Also, some other functions that could be possibly affected by unfortunate timezone/date combinations were fixed.

The functions that were affected: format, parse, getUnixTime, daysToWeeks, hoursToMilliseconds, hoursToMinutes, hoursToSeconds, milliseconds, minutesToMilliseconds, millisecondsToMinutes, monthsToYears, millisecondsToHours, millisecondsToSeconds, minutesToHours, minutesToSeconds, yearsToQuarters, yearsToMonths, yearsToDays, weeksToDays, secondsToMinutes, secondsToHours, quartersToYears, quartersToMonths and monthsToQuarters.
Fixed the Czech locale's formatDistance to include 1 in formatDistance.
Fixed differenceInSeconds and other functions relying on rounding options that can produce a negative 0.
Added a preprocessor to the locales API, enabling fixing a long-standing bug in the French locale. (#1391)
Added missing yearsToDays to the FP submodule.
Made functions using rounding methods always return 0 instead of -0.

Added

Added format alias formatDate with corresponding FormatDateOptions interface.

`v3.2.0`

Compare Source

This release is brought to you by @kossnocorp, @fturmel, @grossbart, @MelvinVermeer, and @jcarstairs-scottlogic.

Fixed

Fixed types compatibility with Lodash's flow and fp-ts's pipe. (#3641)
Fixed inconsistent behavior of roundToNearestMinutes.

Added

Added exports of format, lightFormat, and parse internals that enable 3rd-parties to consume those.

`v3.1.0`

Compare Source

This release is brought to you by @kossnocorp, @makstyle119 and @dmgawel.

Fixed

Fixed the plural form of weeks in Swedish.

Added

Added yearsToDays function.
Added a warning about using protected tokens like Y or D without passing a corresponding option. See #2950.

`v3.0.6`

Compare Source

On this release worked @imwh0im, @jamcry and @tyrw.

Fixed

Fixed bug in areIntervalsOverlapping caused by incorrect sorting (#3614)

`v3.0.5`

Compare Source

This release is brought to you by @goku4199.

Fixed

Fixed internal toDate not processing string arguments properly

`v3.0.4`

Compare Source

This release is brought to you by @kossnocorp.

Fixed

Fixed isWithinInterval bug caused by incorrectly sorting dates (#3623).

`v3.0.3`

Compare Source

Fixed

Rolled back pointing ESM types to the same d.ts files. Instead, now it copies the content to avoid the Masquerading as CJS problem reported by "Are the types wrong?".

`v3.0.2`

Compare Source

Fixed

Fixed yet another issue caused by ESM types by pointing to the same d.ts files.
Added package.json to exports to provide access to tooling.
Fixed TypeScript 5.4 build break by using the latest type names.

`v3.0.1`

Compare Source

Fixed

Fixed an error in certain environments caused by d.mts files exporting only types.

`v3.0.0`

Compare Source

Changed

BREAKING: date-fns is now a dual-package with the support of both ESM and CommonJS. The files exports are now explicitly in the package.json. The ESM files now have .mjs extension.
BREAKING: The package now has a flat structure, meaning functions are now named node_modules/date-fns/add.mjs, locales are node_modules/date-fns/locale/enUS.mjs, etc.
BREAKING: Now all file content’s exported via named exports instead of export default, which will require change direct imports i.e. const addDays = require(‘date-fns/addDays’) to const { addDays } = require(‘date-fns/addDays’).
BREAKING: TypeScript types are now completely rewritten, check out the d.ts files for more information.
BREAKING: constants now is not exported via the index, so to import one use import { daysInYear } from "date-fns/constants";. It improves compatibility with setups that modularize imports like Next.js.
BREAKING: Functions now don’t check the number of passed arguments, delegating this task to type checkers. The functions are now slimmer because of this.
BREAKING The arguments are not explicitly converted to the target types. Instead, they are passed as is, delegating this task to type checkers.
BREAKING: Functions that accept Interval arguments now do not throw an error if the start is before the end and handle it as a negative interval. If one of the properties in an Invalid Date, these functions also do not throw and handle them as invalid intervals.
- areIntervalsOverlapping normalize intervals before comparison, so { start: a, end: b } is practically equivalent to { start: b, end: a }. When comparing intervals with one of the properties being Invalid Date, the function will return false unless the others are valid and equal, given the inclusive option is passed. Otherwise, and when even one of the intervals has both properties invalid, the function will always return false.
- getOverlappingDaysInIntervals now normalizes intervals before comparison, so { start: a, end: b } is practically equivalent to { start: b, end: a }. If any of the intervals’ properties is an Invalid Date, the function will always return 0.
- isWithinInterval now normalizes intervals before comparison, so { start: a, end: b } is practically equivalent to { start: b, end: a }. If any of the intervals’ properties is an Invalid Date, the function will always return false.
- intervalToDuration now returns negative durations for negative intervals. If one or both of the interval properties are invalid, the function will return an empty object.
- The eachXOfInterval functions (eachDayOfInterval, eachHourOfInterval, eachMinuteOfInterval, eachMonthOfInterval, eachWeekendOfInterval, eachWeekendOfMonth, eachWeekendOfYear, eachWeekOfInterval, eachYearOfInterval) now return a reversed array if the passed interval’s start is after the end. Invalid properties will result in an empty array. Functions that accept the step option now also allow negative, 0, and NaN values and return reversed results if the step is negative and an empty array otherwise.
BREAKING: intervalToDuration now skips 0 values in the resulting duration, resulting in more compact objects with only relevant properties.
BREAKING: roundToNearestMinutes now returns Invalid Date instead of throwing an error when nearestTo option is less than 1 or more than 30.
BREAKING: IE is no longer supported.
BREAKING: Now all functions use Math.trunc rounding method where rounding is required. The behavior is configurable on a per-function basis.
BREAKING: Undocumented onlyNumeric option was removed from nn and sv locales. If you relied on it, please contact me.
BREAKING: Flow is not supported anymore. If you relied on it, please contact me.
BREAKING: The locales now use regular functions instead of the UTC version, which should not break any code unless you used locales directly.

Added

All functions that accept date arguments now also accept strings.
All functions now export options interfaces.
Now functions allow passing custom Date extensions like UTCDate. They will detect and use the arguments constructor to generate the result of the same class.
eachMonthOfInterval, eachQuarterOfInterval, eachWeekOfInterval, and eachYearOfInterval now accept the step option like most of the eachXOfInterval functions.
A new interval function that validates interval, emulating the v2 interval functions behavior.
differenceInX functions now accept options and allow setting up roundingMethod that configures how the result is rounded. Math.trunc is the default method.

Configuration

📅 Schedule: (in timezone America/Edmonton)

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 has been generated by Mend Renovate.

… → v2.0.5)

…7.3.0)

its-saffron

AI Automated Review

Full PR review.

Analysis engine: MiniMax-M2.7@https://litellm.jory.dev/v1 (anthropic) — escalated (fast_request_changes,fast_low_confidence)

PR Review: Update date-fns (2.30.0 → 4.4.0)

Recommendation

Approve — This major-version dependency upgrade is safe to merge. All CI checks passed, and the single date-fns function used in the codebase (formatDistanceToNow) maintains backward-compatible API across v2→v3→v4.

Change-by-Change Findings

kubetix-web/package.json: Updated date-fns constraint from ^2.30.0 to ^4.0.0. Straightforward version bump.

kubetix-web/package-lock.json: Regenerated lockfile with date-fns 4.4.0. Notably, @babel/runtime is removed as a transitive dependency — v4 no longer depends on it (v2 had "@babel/runtime": "^7.21.0"). This is a transitive dependency cleanup, not a breaking change to the project.

Required Checks — Explicitly Addressed

✅ check for breaking API changes in updated dependencies

Verified: The codebase uses exactly one date-fns function, confirmed by grep:

import { formatDistanceToNow } from "date-fns"

formatDistanceToNow is a stable function with a backward-compatible API across all v2→v3→v4 releases. The breaking changes in the v2→v3 migration (dual ESM/CJS package, .mjs extensions, removed Babel/Flow type definitions) do not affect the function signature or behavior used here.

The v4 release notes (v4.0.0 through v4.4.0) contain no breaking changes — only CDN deprecation, timezone support enhancements, and bug fixes. The GitHub release page for v4.4.0 confirms: "This release revisits the approach to CDN usage and introduces a new package, @date-fns/cdn and deprecates the date-fns CDN scripts." No API changes.

The CI frontend-build check passed, confirming Next.js compiles successfully with date-fns v4.4.0.

✅ run full test suite after upgrade

Verified via CI status: The CI check results table shows all 8 checks completed with success on commit 2a6d941:

test — Python/unit tests
legacy-test — Python integration tests
frontend-build — Next.js build with the upgraded dependency
e2e-tests — End-to-end tests
lint — Code linting
security — Security scanning
build-and-publish — Docker build
helm-check — Helm chart validation

The full test suite ran post-upgrade and all checks passed. No regressions introduced by the date-fns upgrade.

Standards Compliance

✅ Dependency upgrade follows the pattern established by previous dependency PRs in this repository
✅ Per AGENTS.md, Python major updates require manual review; this is a JavaScript/Node dependency, so manual-review requirement does not apply
✅ Per AGENTS.md .renovaterc.json5 policy: GitHub Actions and Python minor/patch auto-merge; Python major requires manual review. This PR is a JavaScript dependency (not Python), so the automerge policy distinction does not apply here. Manual review is appropriate for a major JS dependency bump, which this review provides
✅ No security advisories flagged for date-fns v4.4.0

Linked Issue Fit

No linked issue — this is a standalone dependency update. The PR title and body correctly describe the scope.

Evidence Provider Findings

No evidence providers are configured for this repository, so no findings section applies.

Tool Harness Findings

No issues encountered. The four planned tool calls completed normally.

Unknowns / Needs Verification

None — the CI frontend-build check passing confirms the upgrade compiles and integrates correctly, and the full test suite confirms no regressions.

Summary

This is a well-tested, low-risk major version upgrade of a pure-utility JavaScript library. The single imported function (formatDistanceToNow) has a stable API across the v2→v4 range, all CI checks passed including the frontend build and e2e tests, and the transitive dependency cleanup (@babel/runtime removal) is expected behavior. Safe to merge.

its-miso Bot added 5 commits July 2, 2026 04:40

ci(github-action): update action azure/setup-helm (v5.0.0 → v5.0.1)

c925bc4

ci(github-action): update action misospace/pr-reviewer-action (v2.0.1…

93bc844

… → v2.0.5)

ci(github-action): update action actions/setup-python (v6.2.0 → v6.3.0)

c20b03a

ci(github-action): update action docker/build-push-action (v7.2.0 → v…

90bb646

…7.3.0)

feat(deps)!: Update dependency date-fns (2.30.0 → 4.4.0)

2a6d941

its-miso Bot added the type/major label Jul 2, 2026

its-saffron Bot approved these changes Jul 2, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat(deps)!: Update dependency date-fns (2.30.0 → 4.4.0)#185

feat(deps)!: Update dependency date-fns (2.30.0 → 4.4.0)#185
its-miso[bot] wants to merge 5 commits into
mainfrom
renovate/date-fns-4.x

its-miso Bot commented Jul 2, 2026

Uh oh!

its-saffron Bot left a comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Conversation

its-miso Bot commented Jul 2, 2026

Release Notes

Changed

Fixed

Fixed

Changed

Fixed

Added

Added

Changed

Fixed

Fixed

Added

Fixed

Added

Added

Fixed

Fixed

Added

Fixed

Added

Fixed

Added

Fixed

Fixed

Fixed

Fixed

Fixed

Fixed

Changed

Added

Configuration

Uh oh!

its-saffron Bot left a comment

Choose a reason for hiding this comment

AI Automated Review

PR Review: Update date-fns (2.30.0 → 4.4.0)

Recommendation

Change-by-Change Findings

Required Checks — Explicitly Addressed

✅ check for breaking API changes in updated dependencies

✅ run full test suite after upgrade

Standards Compliance

Linked Issue Fit

Evidence Provider Findings

Tool Harness Findings

Unknowns / Needs Verification

Summary

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants