Skip to content

Conversation

@edgarrmondragon
Copy link
Contributor

GitHub recently added support for requiring actions to be pinned to a full-length commit SHA1.

Their changelog doesn't mention that composite actions also fail if their own actions are not pinned, which is the case for this project.

Hope this makes sense. I added the commit SHAs using pinact run action.yml.

Footnotes

  1. https://github.blog/changelog/2025-08-15-github-actions-policy-now-supports-blocking-and-sha-pinning-actions/

GitHub recently added support for requiring actions to be pinned to a full-length commit SHA[^1].

Their changelog doesn't mention that composite actions also fail if their own actions are not pinned, which is the case for this project.

Hope this makes sense. I added the commit SHAs using [`pinact run action.yml`](https://github.com/suzuki-shunsuke/pinact).

[^1]: https://github.blog/changelog/2025-08-15-github-actions-policy-now-supports-blocking-and-sha-pinning-actions/
@adriencaccia adriencaccia merged commit 28d7fb8 into CodSpeedHQ:main Oct 17, 2025
37 of 39 checks passed
@adriencaccia
Copy link
Member

Thanks a lot for this @edgarrmondragon!

@edgarrmondragon edgarrmondragon deleted the pin-actions branch October 17, 2025 13:54
@edgarrmondragon
Copy link
Contributor Author

edgarrmondragon commented Oct 23, 2025

@adriencaccia I probably should've mentioned that this will actions/cache will be stuck v4.3.0 unless you manually update it with tool like pinact, or set up Dependabot/Renovate. Either will handle the pinning to a commit SHA automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants