@sourcemeta/jsonschema 15.11.0 → 16.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.markdown CHANGED
@@ -95,6 +95,7 @@ documentation:
95
95
  - [`jsonschema bundle`](./docs/bundle.markdown) (for inlining remote references in a schema)
96
96
  - [`jsonschema upgrade`](./docs/upgrade.markdown) (for upgrading schemas to a newer JSON Schema dialect)
97
97
  - [`jsonschema inspect`](./docs/inspect.markdown) (for debugging references)
98
+ - [`jsonschema rdf`](./docs/rdf.markdown) (for turning instances into Linked Data / JSON-LD)
98
99
  - [`jsonschema codegen`](./docs/codegen.markdown) (for generating code from schemas)
99
100
  - [`jsonschema encode`](./docs/encode.markdown) (for binary compression)
100
101
  - [`jsonschema decode`](./docs/decode.markdown)
@@ -157,7 +158,7 @@ Where `X.Y.Z` is replaced with the desired version. For example:
157
158
  uses: actions/checkout@v4
158
159
 
159
160
  - name: Install the JSON Schema CLI
160
- uses: sourcemeta/jsonschema@v15.11.0
161
+ uses: sourcemeta/jsonschema@v16.1.0
161
162
 
162
163
  # Then use as usual
163
164
  - run: jsonschema fmt path/to/schemas --check
@@ -199,6 +200,17 @@ Keep in mind that it is hard to provide binaries that work across GNU/Linux
199
200
  distributions. We conservatively target Ubuntu and Alpine, but you might need
200
201
  to build from source if your distribution of choice is different.
201
202
 
203
+ > [!NOTE]
204
+ > On GNU/Linux (and other non-macOS, non-Windows platforms), the CLI performs
205
+ > HTTP requests through your system's cURL library, which it loads at runtime.
206
+ > This keeps the binaries distribution-independent and makes them respect your
207
+ > system's TLS trust store. `libcurl` is present on most systems, but if it is
208
+ > missing you can install it through your package manager (for example
209
+ > `apt install libcurl4`, `dnf install libcurl`, or `apk add libcurl`). If it
210
+ > lives in a non-standard location, point the CLI at it by setting the
211
+ > `SOURCEMETA_CORE_CURL_SO` environment variable to the full path of
212
+ > `libcurl.so.4`.
213
+
202
214
  To verify the GPG signature of the checksums file:
203
215
 
204
216
  ```sh
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sourcemeta/jsonschema",
3
- "version": "15.11.0",
3
+ "version": "16.1.0",
4
4
  "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",
5
5
  "main": "npm/main.js",
6
6
  "exports": {