Skip to content

Vulnerability Check Should Not Fail Pipeline #609

@bupd

Description

@bupd

Description

The vulnerability check job in the CI pipeline currently fails when vulnerabilities are found. This blocks PRs and releases even though vulnerabilities may be in dependencies and not actionable immediately.

Current Behavior

  • Dagger VulnerabilityCheckReport uses || true to always pass (correct)
  • But the workflow step still fails with exit 1 if "No vulnerabilities found." is not in the report

Expected Behavior

  • Vulnerability check should report findings in the summary
  • Should not fail the pipeline
  • Allows maintainers to review and address vulnerabilities without blocking CI

Related

Files to Change

  • .github/workflows/default.yaml - Remove exit 1 from vulnerability summary step

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions