fix: secure pip tooling while preserving frozen v1 evidence - #59
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR #58 changes pip in the immutable v1.0.0 package inventory, so the license-snapshot consistency gate correctly fails. Meanwhile, current installation environments need the CVE-2026-13346 fix.
This maintenance change upgrades pip to at least 26.2 before supported installations and in every CI environment, including the fresh wheel venv. It explains the historical inventory in SECURITY.md and adds a regression test that still rejects changing only its pip pin. The frozen constraints, license snapshot, and report are unchanged; no runtime/model dependency or release version is changed.
Validation on Windows:
pip checkpasses, with no other installed package version changed.Linux verification and disposition:
478a5543f6ed27b9f140ff991f528c9c56555f2f.not_used: current installation commands do not consume the historical inventory, and active tooling has been upgraded.The vulnerable historical pin remains historical evidence, so this is not an automatic manifest fix or a claim that the advisory is inaccurate. No new model benchmark or release is part of this maintenance.