@sourcemeta/jsonschema 14.0.3 → 14.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
@@ -83,6 +83,7 @@ documentation:
83
83
  - [`jsonschema bundle`](./docs/bundle.markdown) (for inlining remote references in a schema)
84
84
  - [`jsonschema inspect`](./docs/inspect.markdown) (for debugging references)
85
85
  - [`jsonschema canonicalize`](./docs/canonicalize.markdown) (for static analysis)
86
+ - [`jsonschema codegen`](./docs/codegen.markdown) (for generating code from schemas)
86
87
  - [`jsonschema encode`](./docs/encode.markdown) (for binary compression)
87
88
  - [`jsonschema decode`](./docs/decode.markdown)
88
89
 
@@ -133,7 +134,7 @@ Where `X.Y.Z` is replaced with the desired version. For example:
133
134
  uses: actions/checkout@v4
134
135
 
135
136
  - name: Install the JSON Schema CLI
136
- uses: sourcemeta/jsonschema@v14.0.3
137
+ uses: sourcemeta/jsonschema@v14.1.0
137
138
 
138
139
  # Then use as usual
139
140
  - run: jsonschema fmt path/to/schemas --check
@@ -172,9 +173,8 @@ curl -fsSL https://raw.githubusercontent.com/sourcemeta/jsonschema/main/install
172
173
  ```
173
174
 
174
175
  Keep in mind that it is hard to provide binaries that work across GNU/Linux
175
- distributions, given they often have major differences such as C runtimes (GLIC
176
- vs MUSL). We conservatively target Ubuntu 22.04, but you might need to build
177
- from source if your distribution of choice is different.
176
+ distributions. We conservatively target Ubuntu and Alpine, but you might need
177
+ to build from source if your distribution of choice is different.
178
178
 
179
179
  To verify the GPG signature of the checksums file:
180
180
 
@@ -238,3 +238,9 @@ cmake --install ./build --prefix <prefix> \
238
238
 
239
239
  Where `<prefix>` can be any destination prefix of your choosing, such as `/opt`
240
240
  or `/usr/local`.
241
+
242
+ For performance reasons, the build will take as much advantage of your specific
243
+ machine capabilities. If you desire to build a portable binary, or if the
244
+ aggressive processor-specific optimisations cause any issues (we heard of some
245
+ `Illegal instruction` cases), then configure the project with
246
+ `-DJSONSCHEMA_PORTABLE:BOOL=ON`.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sourcemeta/jsonschema",
3
- "version": "14.0.3",
3
+ "version": "14.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",
5
5
  "main": "npm/main.js",
6
6
  "exports": {