Force schema_version to match the schema it came from #131
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Josh Buker <[email protected]>
joshbuker
force-pushed
the
schema/require-version
branch
from
1be2e44 to
2b20fca
Compare
This was referenced Mar 29, 2023
|
Closing, as this requires that OSV follows SEMVER, which isn't possible due to the compatibility requirements outlined in #132 (comment). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Set to v1.4.1 as that's the next slated version.
This is mostly for completeness' sake when it comes to validating instances of OSV with things like jsonschema. When combined with #130, it clearly defines instances of the data as following their particular semver of the schema.