Packages

ata-validator

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

Upgrading ata-validator from 1.16.1 to 1.16.2

1 release in betweenevery note read

Reading releases, release notes and advisories…

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

Release by release

  1. 1.16.2

    12 Sep 20261 fix
    • fixed

      A schema with unevaluatedProperties or unevaluatedItems reported every failure as one placeholder error, { code: 'unevaluated', message: 'unevaluated property or item' }, with no keyword and no instancePath. The generated code answers the verdict for these schemas but the error generator declines them, and the error path then fell into a stub instead of the interpreted engine, which reports them correctly. A wrong type, a missing required property, a bad format or an enum miss under a root unevaluatedProperties: false all came back as that one line. Failing data is now re-validated by the interpreted engine on that path. Verdicts were never affected. Found by a user comparing error output on a generated config schema. tests/test_unevaluated_error_path.js holds the generated-code path to the interpreter's errors on five shapes, in all three engine modes.