-
-
Notifications
You must be signed in to change notification settings - Fork 888
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
Pin hashes in requirements #7081
Conversation
✅ Deploy Preview for inventree-web-pui-preview canceled.
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #7081 +/- ##
=======================================
Coverage 83.37% 83.37%
=======================================
Files 1039 1039
Lines 45731 45731
Branches 1279 1279
=======================================
Hits 38129 38129
Misses 7329 7329
Partials 273 273
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Why does each package get multiple hashes in the requirements file? |
@SchrodingersGat it dependes on how many files/distributions are offered, this can be seen on Pypi itself too:https://pypi.org/project/certifi/#copy-hash-modal-205cb7d5-a79a-4f73-aeb7-f5c1c778db8c |
Most packages nowaday release 2 files: a source tarball and a wheel (that is a pre-build distribution format) |
Ok! Please fix the conflict and I'll merge straight away |
@SchrodingersGat mergefix is in |
This PR introduces requirement hash pinning. This secures against supply chain attacks in which dependencies are replaced with malicious versions.
It also switches workflows over to use a requirement files.