P004 regression

A workflow has more inline-tool findings than its baseline allows, or any at all while locked at 0.

Severity: error. One finding per workflow, at line 1.

Example

.ci-parity-baseline.json allows .github/workflows/ci.yml two inline-tool findings, and the workflow now has three:

.github/workflows/ci.yml
  1:1     P004 regression    .github/workflows/ci.yml has 3 inline-tool findings, baseline allows 2
  11:14   P001 inline-tool   step "Build" in job "web" runs 'pnpm build' directly

ratchet
  .github/workflows/ci.yml  baseline 2   now 3   REGRESSION

2 errors, 0 warnings, 2 tolerated, 0 allowed

For a workflow at 0, or missing from the baseline, the message is .github/workflows/ci.yml is locked at 0 and has 1 inline-tool findings.

Why it matters

The baseline lets a repository adopt ci-parity with inline steps it hasn’t fixed yet, as long as the count never grows. P004 is what stops it growing.

How to fix it

Replace the new inline step with a task; the P001 finding shows which step is over the count.
If it’s deliberate, allow it.
To accept the higher count, run ci-parity baseline --allow-regression and commit the file.

See also

Last reviewed: 2026-10-28