Skip to content

Changelog 1.5

  • The core functions, which every industry uses.

Release notes of @northguild/gmt 1.5.0, newest first, built from packages/gmt/CHANGELOG.md. Back to Changelog.

The @burglekitt organization logo

In memoriam: @burglekitt. These releases were published under the retired @burglekitt npm scope. The package continues as @northguild/gmt from 1.14.2; install @northguild/gmt.

Released 2026-08-08

  • 39a7030: startOfZoned, endOfZoned, startOfQuarterForZoned, endOfQuarterForZoned, mapZonedHoursInDay, startOfUnix, endOfUnix, startOfQuarterForUnix, and endOfQuarterForUnix accept new disambiguation and offset options (disambiguation: "compatible" | "earlier" | "later" | "reject", defaulting to "compatible"; offset: "prefer" | "use" | "ignore" | "reject", defaulting to "ignore") to control how DST gaps and overlaps are resolved when the function’s boundary computation lands on an ambiguous or nonexistent local time. "reject" returns the function’s sentinel (""/null/[]) instead of silently picking a resolution.

    offset must stay at its default ("ignore") for disambiguation to take effect on these functions — setting it to "prefer" (or "use") can make disambiguation inert, since these functions construct their boundary via Temporal.ZonedDateTime.prototype.with(), which otherwise prefers the source’s existing UTC offset whenever it’s still valid. See docs/dst-disambiguation.md for the full explanation.

    convertPlainDateTimeToZoned, addZoned, and subtractZoned also gain the same offset option for API consistency, but it is permanently inert on those three: their underlying construction path always parses a plain datetime string with no offset embedded, so there is never a stored offset for offset to act on.

  • e2cd46e: convertPlainDateTimeToZoned accepts a new disambiguation option ("compatible" | "earlier" | "later" | "reject", defaulting to "compatible") to control how DST gaps (spring-forward) and overlaps (fall-back) are resolved when attaching a timezone to a plain datetime. "reject" returns "" for any ambiguous or nonexistent local time instead of silently picking one.

  • 2b9d434: addZoned and subtractZoned accept a new disambiguation option ("compatible" | "earlier" | "later" | "reject", defaulting to "compatible") to control how a fall-back (DST-end) overlap is resolved when the arithmetic result lands on an ambiguous local time. "reject" returns "" for an ambiguous result instead of silently picking one.

    This option has no effect on a spring-forward (DST-start) gap: Temporal’s arithmetic always resolves a gap landing unambiguously before disambiguation is evaluated, so all four values produce the same result in that case.

Last updated:

© 2026 NorthGuild · Licences

Code examples: MIT-0. Packages: MIT. Third-party data and components: their own licences, credited where they appear. Everything else: © 2026 NorthGuild, all rights reserved.