Update module github.com/shirou/gopsutil/v4 to v4.26.4#123
Update module github.com/shirou/gopsutil/v4 to v4.26.4#123red-hat-konflux-kflux-prd-rh02[bot] wants to merge 1 commit into
Conversation
Signed-off-by: red-hat-konflux-kflux-prd-rh02 <190377777+red-hat-konflux-kflux-prd-rh02[bot]@users.noreply.github.com>
|
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @red-hat-konflux-kflux-prd-rh02[bot]. Thanks for your PR. I'm waiting for a openshift-hyperfleet member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
📝 WalkthroughWalkthroughThe pull request updates an indirect dependency in Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@go.mod`:
- Line 107: The go.mod was bumped to github.com/shirou/gopsutil/v4 v4.26.4 but
go.sum still only contains checksums for v4.26.3; run a module update to
regenerate checksums (e.g., run `go mod tidy` or `go get -u
github.com/shirou/gopsutil/v4@v4.26.4`) so go.sum is updated with v4.26.4
entries and commits the updated go.sum alongside the Go module change.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Central YAML (base), Organization UI (inherited)
Review profile: ASSERTIVE
Plan: Enterprise
Run ID: a53eb041-c0c8-46b5-8d68-e2ff6531752e
📒 Files selected for processing (1)
go.mod
| github.com/rabbitmq/amqp091-go v1.10.0 // indirect | ||
| github.com/sagikazarmark/locafero v0.12.0 // indirect | ||
| github.com/shirou/gopsutil/v4 v4.26.3 // indirect | ||
| github.com/shirou/gopsutil/v4 v4.26.4 // indirect |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "Checking go.mod entry:"
rg -n 'github\.com/shirou/gopsutil/v4\s+v4\.26\.4' go.mod
echo
echo "Checking go.sum checksum entries:"
rg -n 'github\.com/shirou/gopsutil/v4 v4\.26\.4' go.sum
echo
echo "Optional: show any remaining v4.26.3 references in module files:"
rg -n 'github\.com/shirou/gopsutil/v4 v4\.26\.3' go.mod go.sum || trueRepository: openshift-hyperfleet/hyperfleet-sentinel
Length of output: 197
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "=== Checking ALL gopsutil entries in go.sum ==="
rg -n 'gopsutil' go.sum || echo "No gopsutil entries found in go.sum"
echo
echo "=== Checking go.sum file stats ==="
wc -l go.sum
echo
echo "=== Checking context around where gopsutil should appear (alphabetically) ==="
# gopsutil would appear somewhere after "github.com/gonum" and before "github.com/test"
# Let's check lines that might contain github.com/sh* entries
rg -n 'github\.com/sh' go.sum | head -20Repository: openshift-hyperfleet/hyperfleet-sentinel
Length of output: 632
Update go.sum with checksums for github.com/shirou/gopsutil/v4 v4.26.4.
The go.mod has been updated to v4.26.4, but go.sum still contains checksums only for v4.26.3 (lines 229-230). This creates a mismatch that will cause builds to fail with checksum verification errors. Run go mod tidy or go get -u github.com/shirou/gopsutil/v4@v4.26.4 to regenerate go.sum with the correct checksums before merging.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@go.mod` at line 107, The go.mod was bumped to github.com/shirou/gopsutil/v4
v4.26.4 but go.sum still only contains checksums for v4.26.3; run a module
update to regenerate checksums (e.g., run `go mod tidy` or `go get -u
github.com/shirou/gopsutil/v4@v4.26.4`) so go.sum is updated with v4.26.4
entries and commits the updated go.sum alongside the Go module change.
|
Closing: superseded by renovate.json config in #135 (HYPERFLEET-1095). MintMaker will re-create grouped updates on the next Monday cycle. |
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
This PR contains the following updates:
v4.26.3→v4.26.4Release Notes
shirou/gopsutil (github.com/shirou/gopsutil/v4)
v4.26.4Compare Source
What's Changed
cpu
disk
host
load
mem
net
process
New Contributors
Full Changelog: shirou/gopsutil@v4.26.3...v4.26.4
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
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.