v1.4.1: Now with Apple Silicon

Includes builds for Apple Silicon (e.g. m1, m2, etc) along with minor dependency bumps.

v1.4.0: UTF-16 and BOM handling

Adds support for UTF-16 (LE and BE) encoded JSON files.

In the absence of a BOM, the encoding is detected by a simple heuristic. If the first byte is NUL then UTF-16BE is assumed, if the second byte is NUL then UTF-16LE, otherwise UTF-8.

If the file starts with a BOM this is normally treated as an error for JSON. However, this behavior can be overridden with the new -b flag that will use the BOM to determine the encoding. This is based on the language of section 8.1 of RFC 8259 (the current JSON spec).

Note that UTF-16 already worked for YAML files if a BOM existed (as required by the spec).

See also #13 for more discussion.

v1.3.0: YAML support for documents and schemas

Many thanks to @zendril for adding YAML support in #6. Simply use a .yaml or .yml file where a .json file is allowed. It will be auto-converted for use in JSON Schema validation on the fly.

v1.2.1: Versioning is hard

Forgot to bump the embedded version number in v1.2.0 so updating the Makefile to do it automatically via git tags.

v1.2.0: Windows Support

Thanks to @fgma this updates the handling of file URIs to work in standard cases on Windows (see #2)

v1.1.0: Add `-l <file-list>` argument

New -l <file-list> argument for specifying the JSON docs to validate via paths/globs in a file rather than on the command line directly.

v1.0.0: Initial release

v1.0.0: Initial release