Repository navigation
Update pypi-publish action to 1.14.3. - #460
Conversation
|
Are you sure you have the correct commit hash for 1.14.3? Just eyeballing it I get the impression it has the last 4 items from the old hash tacked onto the end. pypa/gh-action-pypi-publish@7245906 should be the correct hash (7245906fb61fa33a13554f9d5fb856fe61758086). |
dataflake
left a comment
There was a problem hiding this comment.
I think the correct hash is 7245906fb61fa33a13554f9d5fb856fe61758086 - yours has ba33 added to the end, which is from the old 1.14.2 hash.
This fixes the certificates security issue. See https://github.com/pypa/gh-action-pypi-publish/releases/tag/v1.14.3 Note: I manually updated the commit hash and comment. Maybe there is a better way. It should be fine, but I am surprised that the commit hashes do not have the same length.
73e9198 to
06c3ab7
Compare
Coverage Report for CI Build 39926122658Coverage remained the same at 20.538%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
|
Oops, you are right. I already thought it strange that both commit hashes would end with |
This fixes the certificates security issue.
See https://github.com/pypa/gh-action-pypi-publish/releases/tag/v1.14.3
Note: I manually updated the commit hash and comment. Maybe there is a better way. It should be fine, but I am surprised that the commit hashes do not have the same length.