@sourcemeta/jsonschema 16.0.0 → 16.1.0

package/README.markdown

@@ -95,6 +95,7 @@ documentation:
 - [`jsonschema bundle`](./docs/bundle.markdown) (for inlining remote references in a schema)
 - [`jsonschema upgrade`](./docs/upgrade.markdown) (for upgrading schemas to a newer JSON Schema dialect)
 - [`jsonschema inspect`](./docs/inspect.markdown) (for debugging references)
+- [`jsonschema rdf`](./docs/rdf.markdown) (for turning instances into Linked Data / JSON-LD)
 - [`jsonschema codegen`](./docs/codegen.markdown) (for generating code from schemas)
 - [`jsonschema encode`](./docs/encode.markdown) (for binary compression)
 - [`jsonschema decode`](./docs/decode.markdown)
@@ -157,7 +158,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@v16.0.0
+  uses: sourcemeta/jsonschema@v16.1.0
 
 # Then use as usual
 - run: jsonschema fmt path/to/schemas --check
@@ -207,7 +208,7 @@ to build from source if your distribution of choice is different.
 > 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
+> `SOURCEMETA_CORE_CURL_SO` environment variable to the full path of
 > `libcurl.so.4`.
 
 To verify the GPG signature of the checksums file:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sourcemeta/jsonschema",
-  "version": "16.0.0",
+  "version": "16.1.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": {