-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Generate SHA's for released packages and include them in package notes #948
Conversation
- run: | | ||
file=$(ls) | ||
sha=$(sha256sum $file | awk '{ print $1 }') | ||
echo "Computed sha256: $sha for $file" |
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.
helpful for debugging and lets us ensure the sha gets into the build log.
@@ -45,6 +45,12 @@ jobs: | |||
|
|||
build: | |||
needs: check | |||
outputs: | |||
linux-x64-sha: ${{ steps.sha.outputs.linux-x64-sha256 }} |
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.
curious whether ${{ matrix.runtime }}-sha: ${{ steps.compute-sha.outputs.sha }}
would work?
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.
ok to be explicit too... looks like there is another place below where we have to repeat the runtimes, so whatevs :)
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.
other way around repeating platforms in multiple places might be to upload as part of artifact
#948) * Update release.yml Compute Sha's for release builds * Update release notes with shas * Update releaseNote.md * Update release.yml * Update release.yml * Update release.yml * Add Ability to Get Sha's * fix typo * remove debug code
This PR updates the release process to include sha256 hashes of the runner downloads. Users can use these to verify that they have downloaded the correct runner and it has not been tampered with.
Example (fake) runner release is found here