Update @cfworker/json-schema validator library info

[KuSh]

No description provided.

[netlify]

✅ Deploy Preview for condescending-hopper-c3ed30 ready!

Name	Link
🔨 Latest commit	8fe153e
🔍 Latest deploy log	https://app.netlify.com/sites/condescending-hopper-c3ed30/deploys/64073c43175e69000896cff2
😎 Deploy Preview	https://deploy-preview-504--condescending-hopper-c3ed30.netlify.app/implementations
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[gregsdennis]

@jdesrosiers @Julian is this mixed content thing new? The changes have no effect on this.

[jdesrosiers]

is this mixed content thing new?

That wasn't there when I merged website updates last week. It's referring to external links in IETF generated documents. There isn't anything we can do about this even if it was a real problem. I'd say we can merge this PR and have @Relequestual look into the Netlify settings to see if we can turn that check off or at least make it a warning or something.

[gregsdennis]

@awwright is this something that went in as part of your tooling update? (Maybe that was contained to the spec repo)

[Relequestual]

I have no idea why this is failing now when it didn't before.
I asked if this could be turned off back in 2021. The answer was no, and they weren't planning to add that option.

I do note, that on the current verison, the content uses the HTTPS version of that URL...

<link rel="schema.dct" href="[https://purl.org/dc/terms/](view-source:https://purl.org/dc/terms/)" />
https://json-schema.org/draft-04/json-schema-core.html line 421 (when you view source).

I do not know why this PR would trigger that error now though.

[KuSh]

Checks pass after merging main