[red-hat-konflux-kflux-prd-rh02]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: (in timezone Etc/UTC)

• Branch creation
  • Between 12:00 AM and 04:59 AM (* 0-4 * * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[coderabbitai]

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

• Chores
  • Updated locked RHEL 9.9 package records across aarch64, ppc64le, s390x, and x86_64, including refreshed package versions and download metadata.

The RHEL 9.9 RPM lock data is updated for aarch64, ppc64le, s390x, and x86_64. The changes replace selected binary and source package records, including their versions, URLs, sizes, and checksums.

Changes: RHEL 9.9 RPM lock refresh

Layer / File(s)	Summary
Update binary and source RPM records rpms.lock.yaml	Binary and source package records are updated across all four architectures. The records include newer versions and corresponding URLs, sizes, and checksums.

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Merge Risk: Minimal · up to 452be

No merge-blocking issue is identified; artifact availability and checksums remain unverified.

Pre-merge checks: 5

Check name	Status	Explanation
Title check		The title clearly summarizes the RPM lockfile dependency refresh described in the changeset.
Description check		The description lists the RPM package version updates and states that the lock files are being refreshed.
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Recent review info

Run configuration

• Source mode: Auto
• Repository: stackrox/stackrox-mcp
• Branch: release-0.2
• File: .coderabbit.yaml
• Commit: c27ff77
• Layers: Repository YAML (base), Central YAML (inherited), Organization UI (inherited)
• Review profile: ASSERTIVE
• Plan: Enterprise
• Run ID: 4f82aadd-8ffc-4587-941d-3648cb41511d

Commits

Reviewing files that changed from the base of the PR and between c27ff77 and 452be36.

Files selected for processing: 1

• rpms.lock.yaml

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review.

[codecov-commenter]

❌ 2 Tests Failed:

Tests completed	Failed	Passed	Skipped
386	2	384	12

View the full list of 2 ❄️ flaky test(s)

::policy 1

Flake rate in main: 100.00% (Passed 0 times, Failed 222 times)

Stack Traces | 0s run time

- test violation 1
- test violation 2
- test violation 3

::policy 4

Flake rate in main: 100.00% (Passed 0 times, Failed 222 times)

Stack Traces | 0s run time

- testing multiple alert violation messages 1
- testing multiple alert violation messages 2
- testing multiple alert violation messages 3

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}

[github-actions]

E2E Test Results

Commit: 452be36
Workflow Run: View Details
Artifacts: Download test results & logs

=== Evaluation Summary ===

  ✓ list-clusters (assertions: 3/3)
  ✓ cve-cluster-does-not-exist (assertions: 3/3)
  ✓ cve-log4shell (assertions: 3/3)
  ✓ cve-detected-workloads (assertions: 3/3)
  ✓ cve-clusters-general (assertions: 3/3)
  ✓ rhsa-not-supported (assertions: 2/2)
  ✓ cve-cluster-list (assertions: 3/3)
  ~ cve-nonexistent (assertions: 2/3)
      - MaxToolCalls: Too many tool calls: expected <= 5, got 6
  ✓ cve-detected-clusters (assertions: 3/3)
  ✓ cve-multiple (assertions: 3/3)
  ✓ cve-cluster-does-exist (assertions: 3/3)

Tasks:      11/11 passed (100.00%)
Assertions: 31/32 passed (96.88%)
Tokens:     ~55707 (estimate - excludes system prompt & cache)
MCP schemas: ~12562 (included in token total)
Agent used tokens:
  Input:  13040 tokens
  Output: 22187 tokens
Judge used tokens:
  Input:  51957 tokens
  Output: 42290 tokens