Repository navigation
fix(renovate): tidy Go modules after every update - #5832
Conversation
Renovate left stale go.sum lines after Go module bumps, so the tidiness check failed on platform#5764 and platform#5775. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@codex review |
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: Didn't find any major issues. Keep it up! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Readiness at
|
Readiness at
|
Why
Automatic Go library updates keep failing the "modules are tidy" check, because the update bot leaves the old version's checksums behind. Two such updates are stuck right now (#5764, and #5775 which was just evicted from the merge queue for the same reason), and every future Go library update can hit the same wall and need a human-style repair.
What
Tells the update bot to tidy each Go module after it changes it, so its updates arrive already clean and can merge on their own.
No issue: trivial fix.