fix(ci): resync web lockfile blocking Trivy - #1806
Draft
groupthinking with Copilot wants to merge 1 commit into
Draft
fix(ci): resync web lockfile blocking Trivy#1806groupthinking with Copilot wants to merge 1 commit into
groupthinking with Copilot wants to merge 1 commit into
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Copilot
AI
changed the title
[WIP] Fix CI resync web lockfile blocking Trivy
fix(ci): resync web lockfile blocking Trivy
Sep 8, 2026
8 tasks
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
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.
Canonical issue
Root/workspace lockfile drift blocked the
trivyjob before Trivy could start. The failure was in the repo root Docker build path, not in the Python-only PRs that surfaced it.Outcome
Security Scan can get past the web workspace install step again and reach Trivy.
apps/webmanifest for the OpenTelemetry additions that were missing from the lock.npm ci --workspace=apps/web --production --legacy-peer-depssucceeds inside the root Docker build, so Trivy can execute and emit findings.RUN npm ci --workspace=apps/web --production --legacy-peer-depsScope
apps/webdependency graphRisk
Verification
List exact automated and manual checks, tied to the current head SHA
6fda5e8.npx -y npm@10.8.0 ci --workspace=apps/web --production --legacy-peer-depsdocker build -t eventrelay:test -f Dockerfile .trivy image --severity CRITICAL,HIGH --ignore-unfixed eventrelay:testProduction evidence
Not applicable. This change is CI/infrastructure repair for the Security Scan path; no production behavior or deployment surface changes.
Agent handoff