Packages

ata-validator

1.61.3 · 29 Oct 2026MIT21.8k / weekRepositoryHomepagenpmAtom feed

Upgrading ata-validator from 1.16.0 to 1.16.1

1 release in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 1.16.0Newest 1.x, Latest1.61.3
0
changes to make
0
advisories fixed
0
new
1
fix

Release by release

  1. 1.16.1

    12 Sep 20261 fix
    • fixed

      A custom format (formats: { name: fn }, or addFormat on the compat class) next to a shape the combined code generator declines, such as an anyOf sibling, threw _uf_<name> is not defined on the first invalid document instead of reporting the format error. The error-path code generator emitted the call to the format checker without binding it; it now takes the checkers as bound parameters like the other two entry points. Verdicts were never affected, only the error path, and only on that combination. Present since custom formats were added; caught by the 1.16.0 clean-install check. tests/test_user_format_error_path.js covers it, and the compat parity corpus has the scenario.