You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/docs/reference/spec/migration/buildpack-api-0.6-0.7.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,9 @@ Valid `<ext>` extensions are as follows:
27
27
| `application/spdx+json` | `spdx.json`
28
28
| `application/vnd.syft+json` | `syft.json`
29
29
30
-
SBOM files for launch will be included in the application image if the platform api supports it; SBOM files for build may be saved off by the platform prior to the build container exiting. 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).
30
+
SBOM files for launch will be included in the application image if the platform api supports it; SBOM files for build may be saved off by the platform prior to the build container exiting.
31
+
32
+
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.
31
33
32
34
The `[bom]` tables in launch.toml and build.toml are no longer supported.
0 commit comments