A major breaking change was made to the API of this module and then released with only a patch version bump (v3.0.4 -> v3.0.5).

When I asked about this, I received this response:

ory/jsonschema#8 (comment)

Yes, we only use this fork internally though. I'd recommend using the upstream for anyone else

Since the current version of the dependency works fine, it doesn't seem worth the effort to port the code to accommodate the breaking change. It would be better to invest the development resources to replacing this dependency that is not being maintained in a reliable manner (or perhaps to abandoning the too limiting schema-based approach completely).

I thoroughly evaluated all the available Go modules for JSON schema validation during the initial development of Arduino Lint. Most were not at all suitable because they only provide human readable validation output. Arduino Lint requires machine consumable output which can then be interpreted according to the current tool settings and translated to user friendly error and warning messages.

The only module I found that met this requirement was:
https://github.com/santhosh-tekuri/jsonschema
However, I found even it did not provide sufficient machine consumable output under certain schema configurations. Another user had previously encountered this issue andcreated a fork when the main module's maintainer was not receptive tothe proposal. So I used that fork.

It would be worth checking to see if it would now be possible to switch from usinggithub.com/ory/jsonschema to the properly maintained upstreamgithub.com/santhosh-tekuri/jsonschema. There has been quite a lot of development in that module since the time I evaluated it, so maybe the needed capability has been added.

An alternative solution would be to configure the schemas in such a manner as to avoid the limitation that caused me to rejectgithub.com/santhosh-tekuri/jsonschema originally. I think that is possible, but it makes them much more difficult to develop, maintain, and contribute to. The main benefit to the JSON schema-based approach is standardization, so we lose some of that by not providing full compatibility.