@onlyworlds/sdk 4.42.3 → 4.42.4

package/CHANGELOG.md

@@ -5,6 +5,11 @@ earlier history lives in git log only.
 
 ## [Unreleased]
 
+## [4.42.4] - 2026-10-21
+
+### Fixed
+- **`parseDate` refuses a date the typed era does not hold**, rather than reading its number as an absolute year in another era. With a down era Before Gate turning on 6 Frost, "10 Thaw, 1 BG" read as step 39 ("10 Thaw, 2 AG") and "3 Frost, 0 BG" as "3 Frost, 1 BG"; both now answer `not a date in Before Gate`. The absolute reading stays for a step in no era, where `formatStep` prints the absolute year. No date `formatStep` prints changes how it parses: 20,826 round trips over the profile fixture's calendars read the same before and after. Found by Temper in Atlas 1.67.1 (OW Council h58 #9304).
+
 ## [4.42.3] - 2026-10-21
 
 ### Fixed

package/dist/index.js

@@ -3348,7 +3348,11 @@ function parseDate(cfg, input, opts = {}) {
   const viaEra = resolveInYear(absYearForEraYear(cfg, target, year));
   if (isParseError(viaEra)) return viaEra;
   if (eraForStep(cfg, viaEra.step) === target) return viaEra;
-  return resolveInYear(year);
+  const viaAbs = resolveInYear(year);
+  if (era && !isParseError(viaAbs) && eraForStep(cfg, viaAbs.step) !== null) {
+    return { error: `not a date in ${era.name}` };
+  }
+  return viaAbs;
 }
 function isParseError(r) {
   return r.error !== void 0;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@onlyworlds/sdk",
-  "version": "4.42.3",
+  "version": "4.42.4",
   "description": "TypeScript SDK for the OnlyWorlds API - build world-building applications with type safety",
   "type": "module",
   "exports": {