Repository navigation
fix(ci): record the scanner versions MegaLinter now runs - #5847
Conversation
Validate Main fails on main because the organization's Go workflow now runs MegaLinter 10.1.0 (checkov 3.3.15, trivy 0.74.0) for this repository, while the recorded constants still name 10.0.0 (3.3.9, 0.73.0). Move the three constants and the vendored-operator checkov pin together, as the guard and the pin's own comment require. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@codex review for scanner version constants and the vendored checkov pin move together |
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. Can't wait for the next one! 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". |
The pending baseline measurement now has an open delivery record: #5849, linked as a native child of #5843. #2787 is closed, so it no longer tracks the remeasurement mentioned in this PR. The follow-up retains exact scanner versions, complete framework/parse coverage, a same-tree comparison for changed counts, coupled vendoring validation and post-merge hosted acceptance. Updating these constants does not by itself establish a clean scan or complete that follow-up. |
❌MegaLinter analysis: Error❌ REPOSITORY / betterleaks - 11 errors❌ REPOSITORY / checkov - 27 errors❌ HTML / djlint - 8 errors❌ REPOSITORY / grype - 38 errors❌ DOCKERFILE / hadolint - 1 error❌ HTML / htmlhint - 21 errors❌ REPOSITORY / osv-scanner - 1 error❌ GO / revive - 1 error❌ REPOSITORY / secretlint - 1 error❌ BASH / shellcheck - 1 error❌ REPOSITORY / trivy - 1 error❌ YAML / v8r - 1 error❌ YAML / yamllint - 293 errors❌ ACTION / zizmor - 40 errors
|
Blocker: none Cleared 2026-11-04: re-verified 09:18Z: the fix platform#5853 merged 08:01Z; at head 60e6c6f every required check passes (CLEAN). #5843 stays open for its remaining follow-up (#5849), which this PR does not depend on. Previous record (historical): |
devantler
left a comment
There was a problem hiding this comment.
🤖 Generated by the Agentic Engineer
Self-review (fallback — CodeRabbit, Codex and Cursor Bugbot unavailable)
Reviewed commit: 60e6c6f00445d9b63117139703fa9941348fe99f
- CodeRabbit: rate-limited at 2026-11-04T08:28:01Z, retry window until 09:16:58Z (review-lane-health, portfolio-wide); no CodeRabbit artifact on this PR at any head.
- Codex: usage limit since 2026-11-04T08:07:43Z (review-lane-health); recovers only when the maintainer lifts it.
- Cursor Bugbot: usage limit since 2026-11-04T08:07:41Z (review-lane-health); recovers only when the maintainer lifts it.
Checked:
- The three recorded constants now equal what main's failing
Validate Scanner Versionsjob read from the live MegaLinter run (run 41796302144): MegaLinter 10.1.0, checkov 3.3.15, trivy 0.74.0. scripts/update-vendored-operators.shmoves its checkov pin to 3.3.15 in the same commit, as its own same-pin guard requires.- No other script still pins checkov 3.3.9 or trivy 0.73.0 at this head.
- nit (outside the diff): the
.trivyignore.yaml:128comment still says CI runs trivy 0.73.0 on MegaLinter 10.0.0. It is prose only; the re-measurement in #2787 is the place to refresh it.
Verdict: no P0/P1 findings
@coderabbitai review |
Action performed
|
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Readiness at 60e6c6f
Promoting this PR and queueing it at this head. |
Verified after merge: Validate Main run 41824603562 at merge commit |

Why
The main branch check is red. The organization's shared lint workflow now scans this repository with newer scanner releases than the ones the platform records. The guard that compares the two stops main until they match again.
What
Records the scanner releases the shared workflow now runs, and moves the local vendoring check with them, so main is green again. Re-measuring the scan baseline on the new releases is still to do (#5849). The new required scan findings are tracked separately in #5843.
No issue: trivial fix.