Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: no schema with key or ref "https://json-schema.org/draft/2020-12/schema" #20

Closed
andrewpollock opened this issue Aug 29, 2024 · 5 comments

Comments

@andrewpollock
Copy link

Hi,

I'm having a hard time understanding what the problem might be here...

Objective: validate PRs changing a JSON Schema definition itself for correctness

Implementation: ossf/osv-schema@1c585fd

Expected outcome: the change to validation/schema.json is validated for correctness, and any problems surfaced with clear and actionable feedback

Actual outcome: Error: no schema with key or ref "https://json-schema.org/draft/2020-12/schema" is opaque about whether this is a problem with the PR or a misconfiguration of the Action

@andrewpollock
Copy link
Author

ossf/osv-schema#260 is the PR exhibiting this problem

@dsanders11
Copy link
Owner

Thanks for opening an issue! From the linked implementation, it looks like you're using an older version that didn't support that draft version. Can you try using the latest v1.2.0?

andrewpollock added a commit to andrewpollock/osv-schema that referenced this issue Aug 29, 2024
I'm not actually sure how I came to pin at a version less than the
latest...

This should fix the problem seen in dsanders11/json-schema-validate-action#20
Signed-off-by: Andrew Pollock <apollock@google.com>
@andrewpollock
Copy link
Author

Thank you for your speedy response and I have no idea how I came to pin at a version older than the latest 🤦‍♂️

andrewpollock added a commit to ossf/osv-schema that referenced this issue Sep 2, 2024
I'm not actually sure how I came to pin at a version less than the
latest...

This should fix the problem seen in
dsanders11/json-schema-validate-action#20

Signed-off-by: Andrew Pollock <apollock@google.com>
@dsanders11
Copy link
Owner

@andrewpollock, if using the latest version fixed your error, could you go ahead and close out this issue? Thanks!

@andrewpollock
Copy link
Author

I believe this to be a non-issue since upgrading to the latest version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants