chore(deps): update module github.com/bombsimon/logrusr/v2 to v4

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/bombsimon/logrusr/v2	v2.0.1 → v4.1.0

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Release Notes

bombsimon/logrusr (github.com/bombsimon/logrusr/v2)

v4.1.0

Compare Source

What's Changed

• With call depth additive by @​bombsimon in #​28
• Add support for logr.Marshaler by @​bombsimon in #​29

Full Changelog: bombsimon/logrusr@v4.0.0...v4.1.0

v4.0.0

Compare Source

What's Changed

• Adapt FormatFunc return type to the expected logrus.Fields type by @​d1egoaz in #​23
• Bump major version by @​bombsimon in #​24

New Contributors

• @​d1egoaz made their first contribution in #​23

Full Changelog: bombsimon/logrusr@v3.1.0...v4.0.0

v3.1.0

Compare Source

What's Changed

• Fix parallel invocation and also a couple typos per the spellchecker. by @​binaryphile in #​20
• Remove one frame from the default call depth by @​bombsimon in #​21
• Fix GitHub actions by @​bombsimon in #​22

New Contributors

• @​binaryphile made their first contribution in #​20

Full Changelog: bombsimon/logrusr@v3.0.0...v3.1.0

v3.0.0

Compare Source

What's Changed

• Update logr to v1.2.2 and update go.mod to 1.17 by @​aledbf in #​8
• README.md: Replace NewLogger with New by @​cfergeau in #​9
• Update CI, supported versions and README by @​bombsimon in #​10
• Map V-level logging to logrus named logging by @​bombsimon in #​13
• Stop overwriting logger on struct when adding fields by @​bombsimon in #​14
• Simplify severity logging by @​bombsimon in #​15
• Don't create logger in each test case by @​bombsimon in #​16
• V3 release by @​bombsimon in #​17

New Contributors

• @​aledbf made their first contribution in #​8
• @​cfergeau made their first contribution in #​9

Full Changelog: bombsimon/logrusr@v2.0.1...v3.0.0

---

Configuration

📅 Schedule: (UTC)

• 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.

---

• 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.

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 10:46 PM UTC · Completed 10:54 PM UTC
Commit: 01f864b · View workflow run →

[fullsend-ai-review]

Review

Findings

High

• [api-contract] go.mod:37 — The PR changes an indirect dependency from github.com/bombsimon/logrusr/v2 v2.0.1 to github.com/bombsimon/logrusr/v4 v4.1.0. This is problematic for two reasons: (1) go.sum contains only checksums for logrusr/v2 and has no entries for logrusr/v4, which will cause go mod verify and builds to fail; (2) since logrusr is an indirect dependency pulled in by argo-cd/v2 v2.14.21, and Go treats /v2 and /v4 as distinct module paths, manually overriding the indirect entry from /v2 to /v4 does not satisfy argo-cd's actual import of logrusr/v2. After go mod tidy, Go will either revert to /v2 or pull in both /v2 and /v4, making this change incorrect or pointless.
  Remediation: Run go mod tidy to regenerate go.mod and go.sum consistently. This will resolve which version of logrusr the dependency graph actually requires. If only /v2 is needed (as expected given argo-cd v2.14.x), revert this change. The logrusr major version can only be upgraded when the consuming dependency (argo-cd) itself upgrades to use /v4.

[fullsend-ai-review]

See the review comment for full details.

[fullsend-ai-review]

[high] api-contract

The PR changes an indirect dependency from github.com/bombsimon/logrusr/v2 v2.0.1 to github.com/bombsimon/logrusr/v4 v4.1.0. This is problematic for two reasons: (1) go.sum contains only checksums for logrusr/v2 and has no entries for logrusr/v4, which will cause go mod verify and builds to fail; (2) since logrusr is an indirect dependency pulled in by argo-cd/v2 v2.14.21, and Go treats /v2 and /v4 as distinct module paths, manually overriding the indirect entry from /v2 to /v4 does not satisfy argo-cd's actual import of logrusr/v2. After go mod tidy, Go will either revert to /v2 or pull in both /v2 and /v4, making this change incorrect or pointless.

Suggested fix: Run go mod tidy to regenerate go.mod and go.sum consistently. This will resolve which version of logrusr the dependency graph actually requires. If only /v2 is needed (as expected given argo-cd v2.14.x), revert this change. The logrusr major version can only be upgraded when the consuming dependency (argo-cd) itself upgrades to use /v4.