@ultimat3/time 18.0.0 → 19.0.0

package/CLAUDE.md

@@ -36,7 +36,11 @@
   agreeing.** ICU 78 (Bun 1.4) RESOLVES `CET`, `EST`, `EST5EDT`, `GMT`, `MST` and their families
   where ICU 75 threw, so a runtime upgrade alone reopened the golden rule above — silently, and in
   the direction that fails dangerous: an abbreviation names no DST rule. So the judgement is never
-  delegated to `Intl`. `canonicalTimeZone` asserts the structural property itself: a zone is
+  delegated to `Intl`. Re-measured 2026-08-27 when the Bun 1.3 reversal was trialled:
+  `new Intl.DateTimeFormat('en', { timeZone: 'CET' })` still THROWS on 1.3.14 and resolves on 1.4.0,
+  while both list the same 445 zones — so the two ICUs disagree in the direction this rule already
+  refuses, and a structural judgement is the only thing that answers the same on either runtime.
+  That is the whole argument, and it is why the trial changed nothing here. `canonicalTimeZone` asserts the structural property itself: a zone is
   `Area/Location`, and `UTC` is the one legal exception. Never a denylist of the names ICU newly
   accepts — that list grows with every tzdata and ICU release, and no rule in it keeps `CET` out
   while letting `Japan` in, both being one label. The single-label `backward` links go with them

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ultimat3/time",
-  "version": "18.0.0",
+  "version": "19.0.0",
   "description": "UTC instants, DST-correct zone math, cron, durations and Intl formatting with an explicit timezone",
   "license": "MIT",
   "type": "module",
@@ -34,6 +34,6 @@
     "test": "bun test"
   },
   "dependencies": {
-    "@ultimat3/core": "18.0.0"
+    "@ultimat3/core": "19.0.0"
   }
 }