Repository navigation
Pin coverage and PyPI publishing actions - #210
ryanduguid wants to merge 3 commits into
Conversation
|
Hey @ryanduguid ... why do you want to do this? |
|
This pins the coverage and PyPI publishing Action code to fixed commits. The existing |
|
Why do you want to do that? It isn't necessary for reproducibility. Is your motivation security related? I would like to understand what goal you are aiming for, and how this change accomplishes that goal. |
|
Yes, it's security rather than reproducibility. A tag like If you'd rather keep the tags, that's fine. I'll close this. |
This reverts commit 33de493.
Summary
Pin the Coveralls and PyPI publishing actions to the commits currently referenced by
v2andrelease/v1. Keep each moving reference as a comment.Evidence
release-v1tags; both resolve tosha256:a68d05519f6d7e47372aeaddab80b851b69afa89be179ec41775c72c4e3ab2d5.Risk
Future updates to these two actions require an explicit commit-pin update. The publishing action derives its container tag from the action ref; its pinned build supports SHA tags and records a successful image push.
Unverified
Hosted CI and publishing were not exercised. Ruff, formatting, mypy and pytest were not rerun for this two-line workflow change. Existing source findings remain outside this contribution.