ci: set only-fixed on grype scan to skip unfixable CVEs#536
Merged
Conversation
Grype currently fails build-containers on HIGH+ CVEs even when upstream has no available fix (e.g. CVE-2026-32631 git, CVE-2026-27135 nghttp2-libs on Alpine). These block new spec.yaml PRs on base-image drift that the PR author cannot resolve. With only-fixed: true, grype only fails on vulnerabilities that actually have a remediation path, so the gate keeps its meaning without blocking on nothing-to-do findings. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
rdimitrov
approved these changes
Apr 21, 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
only-fixed: trueto the grype scan step inbuild-containers.yml.Why
PR #509 (Pinecone MCP) is currently blocked by three HIGH findings in the generated image:
git(apk)nghttp2-libs(apk)picomatch(bundled in npm)Two of the three have no remediation available, so failing the build on them offers no path to green other than waiting for an upstream patch. With
only-fixed: true, grype still fails when a fix exists (picomatch above would still block until the base image bumps npm) but stops failing on CVEs we can't act on.The base-image bump is still the right long-term fix; this change just keeps the gate actionable in the meantime.
Test plan
build-containerspasses on this PR (no spec.yaml changed, so the grype matrix will skip — sanity-check by landing a subsequent no-op spec change or by rebasing PR feat: add Pinecone MCP server #509 on this)build-containers (npx/pinecone-mcp/spec.yaml)should either go green (if picomatch has flowed through) or fail only on the picomatch fix, not the two apk CVEs🤖 Generated with Claude Code