fix(ci): use uv pip install for mpak-scanner#4
Open
JoeCardoso13 wants to merge 2 commits intomainfrom
Open
Conversation
The workflow installs Python 3.13 via uv, but the scanner was installed with bare pip (system Python, likely 3.12). The fallback silently faked a clean scan report. Switch to uv pip install so mpak-scanner runs under the correct Python.
uvx runs mpak-scanner in an isolated environment with the correct Python, avoiding PATH issues from uv pip install.
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.
Summary
pip install mpak-scannerwithuv pip install mpak-scannerinscan.ymluv, butpipused the system Python (likely 3.12), causingmpak-scanner(which requires ≥3.13) to either fail silently or fake a clean scan report via the fallbackTest plan
Security Scanworkflow passes on the PRmpak-scannerinstalls and runs under Python 3.13🤖 Generated with Claude Code