@sourcemeta/jsonschema 14.0.2 → 14.0.4

package/README.markdown

@@ -133,7 +133,7 @@ Where `X.Y.Z` is replaced with the desired version. For example:
   uses: actions/checkout@v4
 
 - name: Install the JSON Schema CLI
-  uses: sourcemeta/jsonschema@v14.0.2
+  uses: sourcemeta/jsonschema@v14.0.4
 
 # Then use as usual
 - run: jsonschema fmt path/to/schemas --check
@@ -172,9 +172,8 @@ curl -fsSL https://raw.githubusercontent.com/sourcemeta/jsonschema/main/install
 ```
 
 Keep in mind that it is hard to provide binaries that work across GNU/Linux
-distributions, given they often have major differences such as C runtimes (GLIC
-vs MUSL). We conservatively target Ubuntu 22.04, but you might need to build
-from source if your distribution of choice is different.
+distributions. We conservatively target Ubuntu and Alpine, but you might need
+to build from source if your distribution of choice is different.
 
 To verify the GPG signature of the checksums file:
 
@@ -238,3 +237,9 @@ cmake --install ./build --prefix <prefix> \
 
 Where `<prefix>` can be any destination prefix of your choosing, such as `/opt`
 or `/usr/local`.
+
+For performance reasons, the build will take as much advantage of your specific
+machine capabilities. If you desire to build a portable binary, or if the
+aggressive processor-specific optimisations cause any issues (we heard of some
+`Illegal instruction` cases), then configure the project with
+`-DJSONSCHEMA_PORTABLE:BOOL=ON`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sourcemeta/jsonschema",
-  "version": "14.0.2",
+  "version": "14.0.4",
   "description": "The CLI for working with JSON Schema. Covers formatting, linting, testing, and much more for both local development and CI/CD pipelines",
   "main": "npm/main.js",
   "exports": {