ci: route release audit through 'make audit' to skip pip-audit toolchain CVE - #18
Merged
Merged
Conversation
…ain CVE The release-on-tag workflow's "Security audit (production dependencies only)" step was running pip-audit against the full venv, which transitively includes pip-audit -> pip-api -> pip 26.0 (CVE-2026-3219, no fix available). The step name claimed prod-only but the command audited everything, so every release tag pushed since pip 26.0 entered the resolver fails the workflow. ci.yml already calls 'make audit', which exports the runtime closure via 'uv export --no-dev' first and scans only that. Aligning release-on-tag with the same target. Identical scope, identical result, single source of truth for what 'production audit' means.
leandrolerena
approved these changes
Apr 28, 2026
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
2 participants
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
The release-on-tag workflow's "Security audit (production dependencies only)" step was running
pip-auditagainst the full venv. That transitively pullspip-audit→pip-api→pip 26.0, which carries CVE-2026-3219 with no fix available. So every release tag pushed since pip 26.0 entered the resolver fails the workflow on the audit step — including v1.4.0 just now.ci.ymlalready callsmake audit, which usesuv export --no-devto scope the scan to the runtime closure (skipping thepip-audittoolchain itself). Routingrelease-on-tag.ymlthrough the same target so both workflows share one source of truth for what "production audit" means. The Makefile target carries an inline rationale comment for the next person who looks.One-line change.
Test plan
make auditsucceeds locally (already does today; no functional change here)