[pcbeingused333]

The date-time format regex checks the date and time fields with the loose classes [01]\d (month), [0-3]\d (day) and [0-2]\d (hour), and the seconds with [0-5]\d. So it accepts values that cannot be RFC 3339 date-times and rejects one that can:

>>> validate = fastjsonschema.compile({'format': 'date-time'})
>>> validate('2020-19-39T29:00:00Z')   # accepted
>>> validate('1998-12-31T23:59:60Z')   # rejected: RFC 3339 allows the leap second 60

The regex now uses 0[1-9]|1[0-2] for the month, 0[1-9]|[12]\d|3[01] for the day, [01]\d|2[0-3] for the hour (also in the offset), and [0-5]\d|60 for the seconds. The shape of the regex is unchanged: the day is still not checked against the length of the month, and the +hhmm offset form that the existing tests expect stays accepted.

Tests: thirteen rows added to test_datetime in tests/test_format.py (two leap-second values that must be accepted, eleven out-of-range values that must be rejected). Eleven fail on master and all pass with this change; the rest of the suite passes (614 passed, 4 skipped, with tests/benchmarks left out). CHANGELOG.txt has an entry under UNRELEASED.

This change was made with Claude Code.

🤖 Generated with Claude Code