Sign commits for verified programs#1104
Conversation
|
@Woody4618 is attempting to deploy a commit to the Solana Foundation Team on Vercel. A member of the Team first needs to authorize it. |
| --title "chore: update verified programs list" \ | ||
| --body "Automated daily update of verified programs from OSecure." \ | ||
| --base master 2>/dev/null || echo "PR already exists" | ||
| uses: peter-evans/create-pull-request@v7 |
There was a problem hiding this comment.
The action is referenced by a floating semver tag (
@v7) rather than an immutable commit SHA. If the tag is ever re-pointed — whether by the maintainer or a supply-chain compromise — the workflow would silently execute different code. The rest of the actions in this file follow the same pattern, but since this step now has write access (contents: write, pull-requests: write) and produces signed commits, pinning it to the exact SHA is particularly worthwhile here.
| uses: peter-evans/create-pull-request@v7 | |
| uses: peter-evans/create-pull-request@67df67e6d47fc5fe9c6b09c199bde2b88b3058ef # v7 |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Description
The update verified programs gh action did not have signed commits.