-
Notifications
You must be signed in to change notification settings - Fork 83
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
Publish JSON schema to GitHub pages #226
Comments
Thanks for the suggestion! Would you be open to submitting a PR for adding this to |
JamieMagee
added a commit
to JamieMagee/osv-schema
that referenced
this issue
Mar 21, 2024
This allows the JSON schema to be published alongside the rest of the documentation to GitHub pages. The schema will be available at https://ossf.github.io/osv-schema/schema.json. Also created a symlink to the previous repository location of `validation/schema.json` in case anyone is already using that in a `$schema` property Closes ossf#226 Signed-off-by: Jamie Magee <[email protected]>
JamieMagee
added a commit
to JamieMagee/osv-schema
that referenced
this issue
Mar 21, 2024
This allows the JSON schema to be published alongside the rest of the documentation to GitHub pages. The schema will be available at https://ossf.github.io/osv-schema/schema.json. Also created a symlink to the previous repository location of `validation/schema.json` in case anyone is already using that in a `$schema` property Closes ossf#226 Signed-off-by: Jamie Magee <[email protected]>
@oliverchang I created #232 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As far as I can see, the JSON schema is only available at https://raw.githubusercontent.com/ossf/osv-schema/main/validation/schema.json. But
raw.githubusercontent.com
isn't really designed to be used as a CDN, which means that putting it in a$schema
property isn't appropriate.Copying the schema as part of the GitHub pages deployment, to something like
https://ossf.github.io/osv-schema/schema.json
, would be better in the long runThe text was updated successfully, but these errors were encountered: