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
error_message: "Repository is private. The workflow has halted in order to keep the repository name from being exposed in the public transparency log. Set 'private-repository' to override."
79
79
override: ${{ inputs.private-repository }}
@@ -85,7 +85,7 @@ jobs:
85
85
steps:
86
86
- name: Generate random 16-byte value (32-char hex encoded)
error_message: "Repository is private. The workflow has halted in order to keep the repository name from being exposed in the public transparency log. Set 'private-repository' to override."
139
139
override: ${{ inputs.private-repository }}
@@ -145,7 +145,7 @@ jobs:
145
145
steps:
146
146
- name: Generate random 16-byte value (32-char hex encoded)
error_message: "Repository is private. The workflow has halted in order to keep the repository name from being exposed in the public transparency log. Set 'private-repository' to override."
Copy file name to clipboardExpand all lines: RELEASE.md
+5-1
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,11 @@ $ export GH=/path/to/gh
33
33
34
34
## Pre-release tests
35
35
36
-
Needless to say, only think about a release when all the e2e tests in [github.com/slsa-framework/example-package/.github/workflows/](github.com/slsa-framework/example-package/.github/workflows/) are passing. (They run daily).
36
+
Verify the references to the internal Actions by manually running the [release workflow](https://github.com/slsa-framework/slsa-github-generator/actions/workflows/release.yml). Ensure this workflow succeeds.
37
+
38
+
Code freeze the repository for 1-2 days.
39
+
40
+
Verify all the e2e tests in [github.com/slsa-framework/example-package/.github/workflows/](github.com/slsa-framework/example-package/.github/workflows/) are passing. (They run daily).
37
41
38
42
There is one integration test we cannot easily test "live", so we need to simulate it by changing the code: malicious verifier binary in assets. We want to be sure the builder fails if the verifier's binary is tampered with. For this:
0 commit comments