feat: pilot enabling strict mode on all JSON Schema compliant sources #2943
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.
This enables strict mode in the OSV.dev staging environment for all sources in staging that have been deemed already be publishing 100% OSV JSON Schema compliant records, with the notable exception of the RustSec Advisory Database due to rustsec/advisory-db#2135 and the inclusion of PyPA despite pypa/advisory-database#217 (because of pypa/advisory-database#208)
Part of #2188