Skip to content

fix(deps): bump jsonparser v1.1.2 (CVE-2026-32285) — needs Bob deploy approval#121

Draft
garfieldstoun wants to merge 1 commit into
mainfrom
garfield/deps-jsonparser-cve-2026-32285
Draft

fix(deps): bump jsonparser v1.1.2 (CVE-2026-32285) — needs Bob deploy approval#121
garfieldstoun wants to merge 1 commit into
mainfrom
garfield/deps-jsonparser-cve-2026-32285

Conversation

@garfieldstoun

Copy link
Copy Markdown
Contributor

⚠️ Needs Bob's prod-deploy approval before merge

This PR changes go.mod/go.sum, which deploy-backend.yml auto-deploys to prod (build → rsync to tw-mesh → atomic swap → restart). Per CLAUDE.md, prod deploys are Bob's call. Kept as draft so it isn't merged accidentally — mark ready + merge when you're ready to deploy.

What

Verification

  • go build ./... passes locally.
  • CI (lint/test/build) + Trivy run on this PR (Trivy will be green with no ignore needed).

Heads-up: suspected activation-gap in the deploy pipeline

Per the existing note on deploy-backend.yml, there's a suspected bug where the pipeline stages the new binary + writes the deploy marker but the restart may boot the old binary (reports "deployed" while running stale code). Recommend confirming /api/v1/healthz/version returns this PR's SHA after merge.

Resolves the first finding from the Trivy gate (HIGH DoS via malformed JSON,
fixed in v1.1.2) and removes the temporary .trivyignore entry added in #118.

NOTE: this changes go.mod/go.sum -> deploy-backend.yml auto-deploys the backend
to prod on merge to main. Merge only with Bob's prod-deploy approval.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant