-
-
Notifications
You must be signed in to change notification settings - Fork 87
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
Require hashes and wheels for dependencies #248
base: unstable/v1
Are you sure you want to change the base?
Conversation
for more information, see https://pre-commit.ci
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, but I'd rather fix Pip's regression that prevents using constraints with hashes. I don't like abusing constraints as direct deps.
@webknjaz could you for now build and upload the docker image, narrowing the window for a compromise and speeding up usage of the action? |
I've been meaning to merge #230 which will allow this. It seems ready, I just haven't had time to double-check for the last time. I'd like to get to it ASAP. |
@graingert publishing to GHCR is now implemented. |
Hooray! |
Including hashes means new files won't be used as candidates during the installation phase. Requiring wheels ensures that source distributions won't be used as candidates, mitigating the potential to "downgrade" to the sdist by deleting the wheel file for a release.
Both of these options together stops an intrusion in a dependency from being able to impact this GitHub Action.