Skip to content

ci: add report-only pip-audit job - #7

Merged
Xof merged 1 commit into
mainfrom
ci/pip-audit
Jun 21, 2026
Merged

ci: add report-only pip-audit job#7
Xof merged 1 commit into
mainfrom
ci/pip-audit

Conversation

@Xof

@Xof Xof commented Jun 21, 2026

Copy link
Copy Markdown
Collaborator

P6 CI (closes I1)

The pipeline had no dependency vulnerability scan. Adds a third job, audit,
that runs pip-audit.

Report-only by design: the pip-audit step is continue-on-error: true,
so a freshly-published advisory can never turn the pipeline red on
byte-identical code. Only the correctness jobs (test, ruff, mypy) gate a
merge — advisories are surfaced in the job log/summary for triage, not treated
as build failures.

The job installs the package with its [dev,postgres] extras: coddpiece
declares no unconditional runtime dependencies, so without the extras the audit
surface (pytest, ruff, mypy, psycopg, and their transitive deps) would be
effectively empty.

No source/test change. The added YAML was validated locally (three sibling
jobs test / test-postgres / audit; the pip-audit step is non-blocking).

I1: The pipeline had no dependency vulnerability scan. Add an "audit" job that
installs the package with its [dev,postgres] extras (coddpiece declares no
unconditional runtime deps, so the extras are the real audit surface) and runs
pip-audit. The pip-audit step is continue-on-error so a freshly-published
advisory can never turn the pipeline red on byte-identical code -- only
correctness jobs (test, lint, type-check) gate a merge.

Closes I1.
@Xof
Xof merged commit 5348f00 into main Jun 21, 2026
6 checks passed
@Xof
Xof deleted the ci/pip-audit branch June 21, 2026 09:18
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