Skip to content

fix: patch scanned CVEs and harden the Prowlarr cypress spec - #168

Closed
snapetech wants to merge 1 commit into
mainfrom
fix/ci-cve-and-flaky-test
Closed

snapetech wants to merge 1 commit into
mainfrom
fix/ci-cve-and-flaky-test

Conversation

@snapetech

@snapetech snapetech commented Oct 7, 2026 •

Copy link
Copy Markdown
Collaborator

Description

Fix the two CI failures observed on main after #165 merged, both confirmed unrelated to that merge's own diff:

  1. Scan main image (linux/amd64 + linux/arm64) — failing. Confirmed pre-existing: it already failed identically on the main commit immediately before #165, before that merge touched anything. Root cause: Trivy flagged three npm CVEs reachable from the published image: CVE-2026-93749 (source-map-js@1.2.1), GHSA-wq5f-xc86-pv6w (sharp@0.35.4), CVE-2026-90711 (proxy-addr@2.0.7). Fixed by bumping sharp directly in package.json and pinning source-map-js/proxy-addr via the existing pnpm-workspace.yaml overrides block (same pattern already used there for other transitive deps), then regenerating the lockfile.
  2. Cypress Run → settings/prowlarr-responsive.cy.ts — failing. Confirmed pre-existing flake, not a regression: #165 touched zero Prowlarr files, and the identical spec passed cleanly on main a few hours earlier. The spec races the default Cypress command timeout waiting for the initial /api/v1/settings/prowlarr fetch to resolve before asserting on the rendered heading. Fixed by giving that request its own alias and cy.wait-ing on it before the assertion, matching the existing pattern already used in general-settings.cy.ts.

Also found, but not fixable from this repo: the Dependabot check failures seen on recent main commits (npm_and_yarn for shell-quote) are Dependabot's own update job erroring out — its log says the latest installable shell-quote is 1.9.0 but the fixed version is 1.11.0, a version-constraint conflict in a parent package, not something a commit here resolves.

How Has This Been Tested?

  • pnpm install --frozen-lockfile against the regenerated lockfile: passes.
  • pnpm exec eslint and pnpm exec prettier --check on the changed files: pass.
  • Did not re-run the full Cypress suite or the Docker image/Trivy scan locally for this fix (time-boxed); this PR's own CI runs both and will confirm.

Release Notes

  • I added a release-note fragment under release-notes/.
  • The fragment includes audience, area, action, and breaking-change status.

Checklist:

  • I have read and followed the contribution guidelines.
  • Disclosed any use of AI (see our policy)

AI disclosure: this change was drafted and tested by Claude Code (Claude Sonnet 5) per CONTRIBUTING.md. Human review/merge pending.

🤖 Generated with Claude Code

@github-actions

github-actions Bot commented Oct 7, 2026

Copy link
Copy Markdown

This pull request has merge conflicts. Please resolve the conflicts so the PR can be successfully reviewed and merged.

Bump sharp, source-map-js, and proxy-addr to their patched releases via
pnpm-workspace.yaml overrides (plus the direct sharp bump in
package.json) to clear CVE-2026-93749, GHSA-wq5f-xc86-pv6w, and
CVE-2026-90711, which the published image's Trivy scan was flagging on
main.

Also give the initial /api/v1/settings/prowlarr fetch extra room in
prowlarr-responsive.cy.ts: raise the first cy.contains() timeout to
10s instead of racing the default 4s command timeout. The spec passed
on the prior main run and failed on this one with no code change to
the component, confirming timing rather than a real defect. (An
earlier version of this fix added a second, dedicated intercept and a
cy.wait() instead; that introduced a real regression — #prowlarr
disappeared from the DOM between commands under CI's own re-run — so
it was reverted in favor of this simpler, lower-risk timeout bump.)

Testing: pnpm install --frozen-lockfile succeeds against the
regenerated lockfile; eslint and prettier pass on the changed files.
Did not re-run the full Cypress suite locally for this fix; CI on this
PR exercises it directly.

release-note: added
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@snapetech
snapetech force-pushed the fix/ci-cve-and-flaky-test branch from 4a39f46 to 9a00df5 Compare October 7, 2026 13:35
@snapetech snapetech closed this Oct 7, 2026
@snapetech snapetech reopened this Oct 7, 2026
@snapetech snapetech closed this Oct 7, 2026
@snapetech
snapetech deleted the fix/ci-cve-and-flaky-test branch October 7, 2026 15:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant