Skip to content

Hash-lock pip and isolate installation; prepare Beta.8 security release - #18

Merged
morningstarnasser merged 1 commit into
mainfrom
fix/hashlocked-pip
Oct 25, 2026
Merged

morningstarnasser merged 1 commit into
mainfrom
fix/hashlocked-pip

Conversation

@morningstarnasser

Copy link
Copy Markdown
Contributor

Fresh Talos environments inherited pip from the host Python. An actual installed-package scan found pip25.2 advisories (maximum CVSS8.0) despite clean application locks. A user-level ignore-installed setting also left duplicate distribution metadata.

Hash-lock pip26.2.2 in runtime and signature-verifier dependencies, and run installer/updater pip operations with isolated Python and pip configuration. No other package versions change. The clean-install rehearsal now checks the actual pip module and requires exactly one matching distribution. For older updaters with custom pip settings, document the one-time PIP_CONFIG_FILE=/dev/null upgrade command. Prepare Beta.8 without changing the immutable Beta.7 assets.

Validation: 69 targeted tests twice, full3,435pass/3platformskips,277adversarial,101desktop; source hygiene and newdiff secret scan0; all locks and38actuallyinstalled packages OSV0. Signed clean installation, upgrade/rollback and hosted CI qualify the frozen candidate before publication.

@morningstarnasser
morningstarnasser merged commit 2b02094 into main Oct 25, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant