-
-
Notifications
You must be signed in to change notification settings - Fork 273
Generate build provenance attestation during deployment #7419
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
Conversation
|
Thanks @johnbillion! |
|
@johnbillion experienced an issue here with this step https://github.com/pods-framework/pods/actions/runs/14779424219/job/41494876895#step:6:80 |
|
|
I'll take a look |
|
@sc0ttkclark You're using |
|
@johnbillion Doh! Thanks :) Updated for the next release. |
|
@johnbillion just ran another build but it failed, the original PR here did not have the permissions set in the action too: permissions:
id-token: write
attestations: writeAdded for next time. |
|
Whoops I didn't follow my own instructions! |
|
@szepeviktor it hasn't run yet, on the next release it should make it all the way through. |
Description
This uses the WordPress Plugin Attestation action to generate a build provenance attestation for the zip file of Pods. This ties the zip file on wordpress.org back to the GitHub Actions workflow that performed the deployment.
Testing instructions
This isn't testable in isolation because the workflow only runs when you publish a release, but it's used by several other plugins.
Changelog text for these changes
Enhancement: A build provenance attestation is now generated for each deployment to the wordpress.org plugin directory. (@johnbillion)