Changelog: gmt-biome 1.1
Release notes of @northguild/gmt-biome 1.1.0 to 1.1.2, newest first, built from packages/gmt-biome/CHANGELOG.md. Back to Changelog: gmt-biome.
@northguild/gmt-biome
Section titled “@northguild/gmt-biome”Released 2026-11-03
Patch Changes
Section titled “Patch Changes”-
b1cf491: Each package’s npm description and keywords now say what it does.
@northguild/gmtnames time zones, DST, business days and ISO 8601. Each lint package says it bans theDateobject and points to the@northguild/gmtreplacement.The
getTimezoneOffset()lint message in all three lint packages now namesgetTimeZoneOffset(timeZone, instant)from@northguild/gmt, instead of “zoned methods”.The
no-date-library-importsmessage in all three lint packages now names the banned library and links its migration guide on northguild.dev, which maps that library’s calls to their@northguild/gmtreplacements. Moment.js, Day.js, Luxon and date-fns each get their own guide;spacetimelinks the list of guides.All three lint packages now also ban
@date-fns/tz, the time zone package for date-fns v4. The Biome plugin now bans the same packages as the other two, and no longer flags names outside that list such asmoment-tzorluxon-timezone.
Released 2026-09-23
Patch Changes
Section titled “Patch Changes”-
727a3f4: Point the
Date.now()andDate.UTC()diagnostics at@northguild/gmtcalls that exist (Story CORE-8).The
Date.UTC()message and README row recommendedconvertUtcDateTimeToUnix, which@northguild/gmthas never exported. They now nameconvertUtcToUnix, with theZthe UTC string needs. TheDate.now()andDatemessages recommendedgetUnixNow('milliseconds' | 'seconds'), a positional form that@northguild/gmt1.16.0 replaces with an options object.Diagnostic Before After Date.UTC(...) convertUtcDateTimeToUnix('YYYY-MM-DDTHH:mm:ss', 'milliseconds' | 'seconds') convertUtcToUnix('YYYY-MM-DDTHH:mm:ssZ', { epochUnit: 'milliseconds' | 'seconds' }) Date.now()and theDateglobalgetUnixNow('milliseconds' | 'seconds') getUnixNow({ epochUnit: 'milliseconds' | 'seconds' }) The rules match the same code as before. Only the suggestion text changed, in
@northguild/gmt-oxlint,@northguild/gmt-eslintand@northguild/gmt-biomealike.
Released 2026-09-08
Minor Changes
Section titled “Minor Changes”-
4b5d68b: Ban imports of date libraries that wrap or pass native
Dateobjects:moment,moment-timezone,dayjs,luxon,date-fns,date-fns-tz, andspacetime. Reaching for one of these reintroduces exactly the ambient-timezone and DST bugs GMT exists to prevent, so all three linter packages now flag it at the import site rather than waiting for theDatemisuse downstream.Every specifier form is covered — default, named, namespace, side-effect, type-only, subpaths such as
date-fns/format,require(), dynamicimport(), andexport … from. Relative paths that merely contain a banned name (./my-moment-helper) are not flagged.@js-joda/coreis deliberately not banned. Its internal representation is its own value types and it touchesDateonly at the boundary — reading the clock, host zone lookup, andtoDate()interop — so it does not carry the problems this ban targets.New in each package:
no-date-library-imports.gritfor Biome (also folded intoall.grit),no-restricted-importsplus twono-restricted-syntaxselectors for ESLint, and ano-date-library-importsrule for Oxlint, added to its recommended config.
Patch Changes
Section titled “Patch Changes”- 2945c76: Add
repository,homepage, andbugsmetadata to the Biome and ESLint config packages, matchinggmtandgmt-oxlint. npm requires a publicrepositoryfield matching the publishing source in order to generate a provenance attestation, and the automated release workflow publishes via npm trusted publishing, which generates provenance for every public package automatically. Without these fields the two packages could not be published by CI. Also surfaces a repo and issues link on their npm pages.
© 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.