pip
pip require-hashes mode failed because requirements were not fully pinned
In --require-hashes mode, all requirements must have their versions pinned with ==.
pip entered hash-checking mode but found a requirement that was not pinned to an exact version, which makes repeatable secure installs impossible.
Observed message
In --require-hashes mode, all requirements must have their versions pinned with ==.
Why it happens
- A requirement uses a version range instead of an exact pinned version.
- Hash-checking mode was enabled explicitly or implied by an existing --hash entry.
- The requirements file mixes repeatable-install rules with unpinned dependencies.
How to fix it
- Pin every requirement in the file to an exact version using == where hash-checking mode is required.
- Add hashes only after the full set of requirements has been pinned consistently.
- If repeatable secure installs are not intended, remove require-hashes mode rather than using a partially hashed file.
