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: etc/releasing.md
+41-1Lines changed: 41 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -160,7 +160,9 @@ Generate an updated Augmented SBOM as described below.
160
160
161
161
Ensure the `silk-check-augmented-sbom` task is passing on Evergreen for the relevant release branch. If it is passing, nothing needs to be done (unless the SBOM Lite was updated as described above).
162
162
163
-
If the `silk-check-augmented-sbom` task was failing, update the Augmented SBOM document using the following command(s):
163
+
#### Regular Update
164
+
165
+
Update the Augmented SBOM document using the following command(s):
164
166
165
167
```bash
166
168
# Artifactory and Silk credentials.
@@ -189,6 +191,44 @@ Update `etc/third_party_vulnerabilities.md` with any updates to new or known vul
189
191
190
192
Commit the latest version of the Augmented SBOM document into the repo as `etc/augmented.sbom.json`. The Augmented SBOM document does not need to be updated if the `silk-check-augmented-sbom` was not failing (in which case the only changes present would a version bump or timestamp update).
191
193
194
+
#### Instant Update
195
+
196
+
If the Augmented SBOM has not yet been updated in time for a release, a temporary Silk Asset Group may be used instead:
197
+
198
+
```bash
199
+
# Artifactory and Silk credentials.
200
+
.$HOME/.secrets/artifactory-creds.txt
201
+
.$HOME/.secrets/silk-creds.txt
202
+
203
+
# Name of the temporary Silk Asset Group. Do NOT use an existing Silk Asset Group!
0 commit comments