Skip to content

Commit 34c5d16

Browse files
authored
1 parent bbeae84 commit 34c5d16

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

RELEASE.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -38,9 +38,11 @@ There is one integration test we cannot easily test "live", so we need to simula
3838

3939
1. Create a new release for your fork of the slsa-verifier repository with a malicious binary.
4040
```
41-
$ echo hello > slsa-verifier-linux-amd64
41+
# Create a release
4242
$ "$GH" release -R "$VERIFIER_REPOSITORY" create "$VERIFIER_TAG" --title "$VERIFIER_TAG" --notes "pre-release tests for builder $BUILDER_TAG $(date)"
4343
$ # Note: this will create a release workflow: cancel it in the GitHub UI.
44+
# Upload a malicious binary.
45+
$ echo hello > slsa-verifier-linux-amd64
4446
$ "$GH" release -R "$VERIFIER_REPOSITORY" upload "$VERIFIER_TAG" slsa-verifier-linux-amd64
4547
```
4648
2. Ensure your fork of the builder is at the same commit hash as the offical builder's `$BUILDER_TAG` release.

0 commit comments

Comments
 (0)