Repository navigation
Run vulnerability scans weekly and update Go to 1.26.11 - #5067
Merged
Merged
Conversation
Codex Review Summary: ✅ CompletedThis 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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Repeated PR failures were reporting GO-2026-6859 in the pinned Go 1.26.10 toolchain. Update to Go 1.26.11 and have tests, lint and releases read the toolchain from go.mod. Upgrade test setup-go to v5 so it supports the toolchain directive.
Run govulncheck on Mondays at 08:23 UTC and on manual dispatch, rather than on every push and PR. Pin the scanner to v1.10.0. Findings and scanner errors still fail the maintenance run; retain the existing explicit allowlist. Update the maintenance documentation.
Validation: Go 1.26.11 go build ./... passed; govulncheck v1.10.0 reports zero reachable vulnerabilities (four module-level advisories remain without reachable calls). Workflow YAML parses; scan shell checked for clean, allowlisted, new-vulnerability and scanner-error results; git diff --check passed. Full unit suite not rerun for this configuration change.
Repository setting: if govulncheck is configured as a required status check, remove it from branch protection when merging. The GitHub integration returned 403 when inspecting that setting, so its current requirement status could not be verified.