Update migration guide to reflect buildpacks/spec#286

Natalie Arellano · Natalie Arellano · commit 1e56d12c9971 · 2022-01-26T12:21:45.000-05:00
Signed-off-by: Natalie Arellano &lt;narellano@vmware.com&gt;
diff --git a/content/docs/reference/spec/migration/buildpack-api-0.6-0.7.md b/content/docs/reference/spec/migration/buildpack-api-0.6-0.7.md
@@ -31,7 +31,7 @@ SBOM files for launch will be included in the application image if the platform
 
 Layer-associated SBOM files will be cached and restored to the buildpack layers directory on re-builds of the same image (much like the `<layers>/<layer>.toml` metadata file). `<layers>/launch.sbom.<ext>` and `<layers>/build.sbom.<ext>` must be re-created on each build.
 
-The `[bom]` tables in launch.toml and build.toml are no longer supported.
+The `[bom]` tables in launch.toml and build.toml are deprecated, but remain supported to enable backwards compatibility with platforms implementing Platform API < 0.8.
 
 ### New fields in buildpack descriptor
 
diff --git a/content/docs/reference/spec/migration/platform-api-0.7-0.8.md b/content/docs/reference/spec/migration/platform-api-0.7-0.8.md
@@ -45,4 +45,4 @@ Note that the `<layers>/sbom/build` directory is NOT present in the application
 
 #### Backwards compatibility - older buildpacks
 
-Platforms can continue to retrieve BOM information output by buildpacks implementing Buildpack API < 0.7 by reading the `bom` key in the `io.buildpacks.build.metadata` label (for run-time dependencies), and by saving off report.toml prior to the build container exiting (for build-time dependencies). 
+Platforms can continue to retrieve BOM information in the legacy format (if output by buildpacks) by reading the `bom` key in the `io.buildpacks.build.metadata` label (for run-time dependencies), and by saving off report.toml prior to the build container exiting (for build-time dependencies).

Original file line number	Diff line number	Diff line change
@@ -45,4 +45,4 @@ Note that the `<layers>/sbom/build` directory is NOT present in the application
`45`	`45`
`46`	`46`	`#### Backwards compatibility - older buildpacks`
`47`	`47`
`48`		-Platforms can continue to retrieve BOM information output by buildpacks implementing Buildpack API < 0.7 by reading the `bom` key in the `io.buildpacks.build.metadata` label (for run-time dependencies), and by saving off report.toml prior to the build container exiting (for build-time dependencies).
	`48`	+Platforms can continue to retrieve BOM information in the legacy format (if output by buildpacks) by reading the `bom` key in the `io.buildpacks.build.metadata` label (for run-time dependencies), and by saving off report.toml prior to the build container exiting (for build-time dependencies).