We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Discovered this while discussing #132
Currently, the canonical url for the schema is: https://raw.githubusercontent.com/ossf/osv-schema/v<SEMVER>/validation/schema.json
https://raw.githubusercontent.com/ossf/osv-schema/v<SEMVER>/validation/schema.json
For example, 1.4.0 resolves to: https://raw.githubusercontent.com/ossf/osv-schema/v1.4.0/validation/schema.json
1.4.0
1.0.0 is historically important due to schema_version being null is implied to be 1.0.0, however currently that 404s: https://raw.githubusercontent.com/ossf/osv-schema/v1.0.0/validation/schema.json
1.0.0
schema_version
This should be added or backported so that it is consistent and can be used by validators.
The text was updated successfully, but these errors were encountered:
Looks like this is a case of releasing https://github.com/ossf/osv-schema/releases/tag/1.0.0
Sorry, something went wrong.
I've made a v1.0.0 release and https://raw.githubusercontent.com/ossf/osv-schema/v1.0.0/validation/schema.json now works.
A v1.0.0 release always warrants one or more beers 🥂
No branches or pull requests
Discovered this while discussing #132
Currently, the canonical url for the schema is:
https://raw.githubusercontent.com/ossf/osv-schema/v<SEMVER>/validation/schema.json
For example,
1.4.0
resolves to:https://raw.githubusercontent.com/ossf/osv-schema/v1.4.0/validation/schema.json
1.0.0
is historically important due toschema_version
being null is implied to be1.0.0
, however currently that 404s:https://raw.githubusercontent.com/ossf/osv-schema/v1.0.0/validation/schema.json
This should be added or backported so that it is consistent and can be used by validators.
The text was updated successfully, but these errors were encountered: