bump JSON schema

Signed-off-by: Will Murphy <will.murphy@anchore.com>
anchore · May 24, 2024 · 0879364 · 0879364
1 parent 47bebd5
commit 0879364
Show file tree

Hide file tree

Showing 4 changed files with 2,417 additions and 3 deletions.
diff --git a/internal/constants.go b/internal/constants.go
@@ -3,5 +3,5 @@ package internal
 const (
 	// JSONSchemaVersion is the current schema version output by the JSON encoder
 	// This is roughly following the "SchemaVer" guidelines for versioning the JSON schema. Please see schema/json/README.md for details on how to increment.
-	JSONSchemaVersion = "16.0.9"
+	JSONSchemaVersion = "16.0.10"
 )
diff --git a/schema/json/README.md b/schema/json/README.md
@@ -22,7 +22,7 @@ Given a version number format `MODEL.REVISION.ADDITION`:
 
 ## Adding a New `pkg.*Metadata` Type
 
-When adding a new `pkg.*Metadata` that is assigned to the `pkg.Package.Metadata` struct field you must add a test case to `test/integration/catalog_packages_cases_test.go` that exercises the new package type with the new metadata.
+When adding a new `pkg.*Metadata` that is assigned to the `pkg.Package.Metadata` struct field you must add a test case to `cmd/syft/internal/test/integration/catalog_packages_cases_test.go` that exercises the new package type with the new metadata.
 
 Additionally it is important to generate a new JSON schema since the `pkg.Package.Metadata` field is covered by the schema.