fromJSONSchema date-time rejects valid RFC 3339 offsets

[agcty]

fromJSONSchema({ type: "string", format: "date-time" }) currently maps to z.iso.datetime() and rejects valid RFC 3339 timestamps with numeric UTC offsets.

const schema = z.fromJSONSchema({ type: "string", format: "date-time" });

schema.parse("2026-07-29T14:30:00Z"); // accepted
schema.parse("2026-07-29T16:30:00+02:00"); // rejected

JSON Schema defines date-time using RFC 3339, where both Z and numeric offsets are valid. A local timestamp without an offset should remain invalid.

The mapping can preserve that behavior by using z.iso.datetime({ offset: true }). Authored JSON Schema constraints such as pattern should continue to compose with the format check.

[pullfrog]

Changed z.iso.datetime() to z.iso.datetime({ offset: true }) in the fromJSONSchema date-time format mapping so it accepts valid RFC 3339 timestamps with numeric UTC offsets (e.g. +02:00, -05:00). Added a test covering both Z and offset forms, plus rejection of bare local timestamps.

PR: #6297

Task list (4/4 completed)

• Investigate the issue: verify fromJSONSchema date-time mapping
• Fix the mapping to use { offset: true }
• Add test for date-time format in from-json-schema test
• Run existing tests, commit and push

  ^{｜ View workflow run ｜ via Pullfrog ｜ Using DeepSeek Pro (free via Pullfrog for OSS) (Claude Opus not used — the program covers this model; add its provider key to run your pick) ｜ 𝕏}