fix(ci): resolve new govulncheck advisories (pgx bump + docker exclusions)

[michaelmcnees]

Summary

Govulncheck started failing across the repo on four newly-published Go advisories in existing dependencies. The workflow runs govulncheck@latest against the live vuln DB, so these began failing on their own (independent of any code change) and affect main as well. This triages each: fix what's fixable, allowlist what isn't.

Changes

• github.com/jackc/pgx/v5 v5.9.0 → v5.9.2 — fixes GO-2026-5004 (SQL injection via the non-default simple protocol with dollar-quoted literals). This is a real, patched vulnerability, so it's fixed rather than suppressed.
• Allowlist 3 docker/docker advisories in the CI govulncheck exclusion list (.github/workflows/engine-ci.yml) — GO-2026-5617, GO-2026-5668, GO-2026-5746 (docker cp / archive host-path issues). docker/docker and moby/moby have no patched release (only moby/moby/v2 is fixed), so these join the existing docker/docker exclusions. The underlying dependency upgrade is tracked by Upgrade github.com/docker/docker to v29 (CVE-2026-34040, CVE-2026-42306) #151.

Testing

• make test — not affected (no engine logic changed); CI will run it
• make lint — go build ./... passes with pgx v5.9.2
• New tests added — n/a (dependency + CI-config change)

Related Issues

Relates to #151 (docker/docker upgrade). Unblocks Govulncheck on #162 and other open PRs once merged to main.

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

@michaelmcnees, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 45 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 60f522b9-95c4-4343-a621-dd9053e3c798

📥 Commits

Reviewing files that changed from the base of the PR and between c8e74a0 and 330a128.

⛔ Files ignored due to path filters (1)

• packages/engine/go.sum is excluded by !**/*.sum

📒 Files selected for processing (3)

• .changeset/govulncheck-advisories.md
• .github/workflows/engine-ci.yml
• packages/engine/go.mod

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/govulncheck-advisories

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}