@sourcemeta/jsonschema 15.10.1 → 16.0.0

package/README.markdown

@@ -122,6 +122,16 @@ ontology design, linting, unit testing, CI/CD integration, and more:
 
 [![JSON Schema Conference 2024 - Applying software engineering practices to JSON Schemas](https://img.youtube.com/vi/wJ7bK22n3IU/0.jpg)](https://www.youtube.com/watch?v=wJ7bK22n3IU)
 
+Going Further
+-------------
+
+The JSON Schema CLI handles the local development and CI/CD side of schema
+management. For teams that need to publish, discover, and govern schemas across
+an organisation, [Sourcemeta One](https://www.sourcemeta.com) is a self-hosted
+JSON Schema registry that pairs directly with this CLI. It is designed by the
+same team, requires no database, deploys as a single Docker container, and is
+free to deploy.
+
 Installation
 ------------
 
@@ -147,7 +157,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@v15.10.1
+  uses: sourcemeta/jsonschema@v16.0.0
 
 # Then use as usual
 - run: jsonschema fmt path/to/schemas --check
@@ -189,6 +199,17 @@ Keep in mind that it is hard to provide binaries that work across GNU/Linux
 distributions. We conservatively target Ubuntu and Alpine, but you might need
 to build from source if your distribution of choice is different.
 
+> [!NOTE]
+> On GNU/Linux (and other non-macOS, non-Windows platforms), the CLI performs
+> HTTP requests through your system's cURL library, which it loads at runtime.
+> This keeps the binaries distribution-independent and makes them respect your
+> system's TLS trust store. `libcurl` is present on most systems, but if it is
+> missing you can install it through your package manager (for example
+> `apt install libcurl4`, `dnf install libcurl`, or `apk add libcurl`). If it
+> lives in a non-standard location, point the CLI at it by setting the
+> `SOURCEMETA_JSONSCHEMA_CURL_SO` environment variable to the full path of
+> `libcurl.so.4`.
+
 To verify the GPG signature of the checksums file:
 
 ```sh
@@ -258,16 +279,6 @@ aggressive processor-specific optimisations cause any issues (we heard of some
 `Illegal instruction` cases), then configure the project with
 `-DJSONSCHEMA_PORTABLE:BOOL=ON`.
 
-Going Further
--------------
-
-The JSON Schema CLI handles the local development and CI/CD side of schema
-management. For teams that need to publish, discover, and govern schemas across
-an organisation, [Sourcemeta One](https://www.sourcemeta.com) is a self-hosted
-JSON Schema registry that pairs directly with this CLI. It is designed by the
-same team, requires no database, deploys as a single Docker container, and is
-free to deploy.
-
 License
 -------
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sourcemeta/jsonschema",
-  "version": "15.10.1",
+  "version": "16.0.0",
   "description": "The CLI for working with JSON Schema. Covers formatting, linting, testing, and much more for both local development and CI/CD pipelines. By a member of the JSON Schema Technical Steering Committee",
   "main": "npm/main.js",
   "exports": {