@sourcemeta/jsonschema 16.6.0 → 16.8.0

package/README.markdown

@@ -158,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.6.0
+  uses: sourcemeta/jsonschema@v16.8.0
 
 # Then use as usual
 - run: jsonschema fmt path/to/schemas --check
@@ -284,7 +284,9 @@ License
 -------
 
 This project is released under the terms of the [GNU Affero General Public
-License v3.0](./LICENSE).
+License v3.0](./LICENSE). By contributing to this project, you agree to our
+organisation-wide [contribution
+guidelines](https://github.com/sourcemeta/.github/blob/main/CONTRIBUTING.md).
 
 **A note for enterprises:** Using the JSON Schema CLI as a tool during local
 development or as part of your CI/CD pipelines does not trigger the AGPL
@@ -293,3 +295,8 @@ yours. This is the same way that managing your proprietary code with
 [Git](https://git-scm.com) does not make your code subject to the
 [GPL](https://www.gnu.org/licenses/gpl-3.0.en.html). For any other use, please
 refer to the full [license](./LICENSE).
+
+*If you still require a non-copyleft license to run this tool inside your
+organisation, see our [licensing page](https://www.sourcemeta.com/licensing/)
+and reach out to [hello@sourcemeta.com](mailto:hello@sourcemeta.com) to discuss
+further*

package/package.json

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