-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Update release docs #3589
fix: Update release docs #3589
Conversation
Signed-off-by: Ramon Petgrave <[email protected]>
Signed-off-by: Ramon Petgrave <[email protected]>
Signed-off-by: Ramon Petgrave <[email protected]>
Signed-off-by: Ramon Petgrave <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a little bit concerned that thesesed
expressions are hard to maintain, but since they were here from before the PR, I think it should be ok
Signed-off-by: Ramon Petgrave <[email protected]>
@@ -163,7 +163,7 @@ There is one integration test we cannot easily test "live", so we need to simula | |||
using this command: | |||
|
|||
```shell | |||
sed -i "s/uses: slsa-framework\/slsa-github-generator\/\.github\/actions\/generate-builder@\(main\|v[0-9]\+\.[0-9]\+\.[0-9]\+\(-rc\.[0-9]\+\)\?\)/uses: ${BUILDER_REPOSITORY/\//\\\/}\/.github\/actions\/generate-builder@${BUILDER_TAG}/" .github/workflows/builder_go_slsa3.yml | |||
sed -i "s/uses: slsa-framework\/slsa-github-generator\/\.github\/actions\/generate-builder@\(main\|v[0-9]\+\.[0-9]\+\.[0-9]\+\(-rc\.[0-9]\+\)\?\)/uses: ${BUILDER_REPOSITORY/\//\/}\/.github\/actions\/generate-builder@${BUILDER_TAG}/" .github/workflows/builder_go_slsa3.yml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Were these commands not working for some reason?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not on my machine
I totally sympathize with this. I think the release process is entirely too manual but it's difficult to automate. Ideally we wouldn't need to do this but I think we need to iterate to improve as best we can. |
Co-authored-by: Ian Lewis <[email protected]> Signed-off-by: Ramon Petgrave <[email protected]>
Co-authored-by: Ian Lewis <[email protected]> Signed-off-by: Ramon Petgrave <[email protected]>
Making the `download-artifacts.sh` script be more useful. Before, it would error upon seeing some zip files that it doesn't expect to be in the GH release. I think the script is just a bit outdated. But for now, I think we should bypass that, since the script is already written to know which of the final files within the archives are actually needed. related PR slsa-framework/slsa-github-generator#3589 Signed-off-by: Ramon Petgrave <[email protected]>
Summary
A few fixes and additions to the release docs.
sed
commandsrelated PR slsa-framework/slsa-verifier#761
Testing Process
Manual testing locally.
Checklist