Repository navigation
build(deps): refresh Google clients and tracking-worker tooling - #1274
Conversation
0f94600 to
11b7d28
Compare
|
🦞👀 Pull request received. I will update this pull request when review starts. ClawSweeper review completeClawSweeper finished reviewing this revision. The review result is being finalized. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex review: needs maintainer review before merge. What this changesThis PR updates Google, MCP, networking, and tracking-worker dependencies with matching lockfiles and an Unreleased changelog entry. Example: Building gog and the tracking worker from this PR
Review scores
ProductKind: Maintenance · Worth it: Yes · Fix scope: Complete Merge readiness✅ Ready for maintainer review Keep this maintainer-authored dependency refresh open: the updates are absent from main, all checks pass on the reviewed head, and inspection found no actionable defect. Priority: P3 Before mergeNone. FindingsNone. Agent review detailsHow this fits togetherGo dependencies support the CLI's Google API requests, MCP stdio server, and HTML processing; worker dependencies provide Cloudflare types, local development, and deployment tooling. flowchart LR
A[CLI commands] --> B[Go client dependencies]
B --> C[Google APIs]
D[MCP client] --> E[gog stdio server]
E --> A
F[Worker source] --> G[Wrangler tooling]
G --> H[Cloudflare Worker]
Technical reviewBest possible solution: Land the focused dependency refresh while preserving the existing toolchain, supply-chain constraints, and worker security pins. Do we have a high-confidence way to reproduce the issue? This is dependency maintenance without a claimed application bug; the review inspected source and supplied validation without running target code. Is this the best way to solve the issue? Updating the existing manifests and native lockfiles is appropriately scoped, and no replacement layer or application refactor is needed. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against 8c5c062ad9f8. Provenance checked
TestingProof path: in-process harness. SecurityNone. EvidenceWhat I checked:
Likely related people:
LabelsLabel changes:
Label justifications:
Rating scale6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior. WorkflowClawSweeper edits this one comment on every review. Comment Reviewed October 27, 2026, 4:13 PM ET / 20:13 UTC. |
|
Landed as 82e7fd6. Validation: Final-head CI passed Linux, minimum Go, macOS, Windows, and the worker dry build. Docker and CodeQL passed too. The release dry run on merged main passed using the documented current version 0.47.1; it did not publish or tag a release. |
Refresh the supported Go dependency graph: MCP 1.4.0, x/net 0.62.0, Google API 0.309.0, gRPC 1.85.0, and matching genproto revisions. Update the tracking worker to Cloudflare types 5.20261026.1 and Wrangler 4.153.0 with its lockfile.
Keep the documented Go 1.26 minimum, Go 1.27.3 build toolchain, 24-hour pnpm release cooldown, and existing workerd/security overrides. No runtime or release version changes.
Validation: dependency and lockfile review is clean. Full remote Go checks and vulnerability scanning passed; worker lint/type/tests are tracked in the proof comment. The normal PR workflow covers the worker dry build, Linux, minimum Go, macOS, Windows, and container build.