-
Notifications
You must be signed in to change notification settings - Fork 30
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
wrap actions/attest-build-provenance #211
Conversation
4a80625
to
bf2e88e
Compare
26aef12
to
2db573f
Compare
Signed-off-by: Brian DeHamer <[email protected]>
2db573f
to
3b758b9
Compare
- id: translate-output | ||
if: runner.os != 'Windows' | ||
shell: bash | ||
run: | | ||
read -r line < ${{ steps.attest.outputs.bundle-path }} | ||
echo "bundle=$line" >> $GITHUB_OUTPUT |
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.
The primary difference between the early-access action and the public action is the way the action output is handled:
- In the early-access action, the JSON-serialized bundle is passed back in the
bundle
output variable. - In the new action, any attestation bundles are written to a file and the path to that file is passed back in the
bundle-path
output variable.
This bit translates the new scheme to the old one for backward compatibility. We don't handle Windows cause there's no easy way to handle file paths on both Windows and non-Windows runners.
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.
The only user I'd worry about for the Windows platform is Homebrew... but I believe yesterday they switched to actions/attest-build-provenance
so I think we can proceed!
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.
Also, I checked and they are not using the action output
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 did not review the 101,076 lines you deleted 😐
- id: translate-output | ||
if: runner.os != 'Windows' | ||
shell: bash | ||
run: | | ||
read -r line < ${{ steps.attest.outputs.bundle-path }} | ||
echo "bundle=$line" >> $GITHUB_OUTPUT |
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.
The only user I'd worry about for the Windows platform is Homebrew... but I believe yesterday they switched to actions/attest-build-provenance
so I think we can proceed!
Signed-off-by: Brian DeHamer <[email protected]>
Replace local implementation with a call to the public
actions/attest-build-provenance
action.This will ensure that anyone who is still referencing the private beta version of the action is getting all of the updates and bug fixes of the public action.
Also includes a deprecation warning in the job summary: