Update module github.com/cenkalti/backoff/v4 to v7

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

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/cenkalti/backoff/v4	v4.3.0 → v7.0.0

---

Release Notes

cenkalti/backoff (github.com/cenkalti/backoff/v4)

v7.0.0

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

v5.0.3

Compare Source

v5.0.2

Compare Source

v5.0.1

Compare Source

v5.0.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "on monday"
• 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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign aredenba-rh for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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

[coderabbitai]

Warning

Review limit reached

@red-hat-konflux-kflux-prd-rh02[bot], you've reached your PR review limit, so we couldn't start this review.

Next review available in: 54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 862a9758-4661-4db9-8a18-e5af33c09d72

📥 Commits

Reviewing files that changed from the base of the PR and between 7d2f51c and b90031b.

📒 Files selected for processing (1)

• go.mod

📝 Walkthrough

Walkthrough

Single-line go.mod change replacing the indirect dependency github.com/cenkalti/backoff/v4 (v4.3.0) with github.com/cenkalti/backoff/v7 (v7.0.0).

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

Changes

File	Change
go.mod	Indirect requirement bumped from backoff/v4@v4.3.0 to backoff/v7@v7.0.0

Security note: Major version jump (v4→v7) on a transitive dependency introduces unaudited supply-chain surface. No go.sum hash diff provided for verification — confirm checksum integrity and review upstream changelog for v5/v6/v7 breaking changes and any CVE advisories against cenkalti/backoff before merge. No exported/public API of this repo is affected directly, but transitive consumers of backoff's retry/exponential-backoff logic should be validated for behavioral drift.

Related issues: None provided.

Related PRs: None provided.

Suggested labels: dependencies, go.mod, supply-chain

Suggested reviewers: None specified in input.

🚥 Pre-merge checks | ✅ 11

✅ Passed checks (11 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Sec-02: Secrets In Log Output	✅ Passed	Only go.mod changed; no slog/logr/zap/fmt.Print* code touched, so no token/password/credential/secret log exposure (CWE-532).
No Hardcoded Secrets	✅ Passed	Only go.mod changed; no hardcoded secret literals, embedded creds, or long base64 blobs found (no CWE-798/CWE-522 indicators).
No Weak Cryptography	✅ Passed	PASS: No CWE-327/CWE-759 findings; repo has no crypto/md5, crypto/des, crypto/rc4, ECB, SHA1-for-security, or unsafe secret compares.
No Injection Vectors	✅ Passed	Only go.mod changed; no CWE-89/78/79/502 injection patterns were introduced.
No Privileged Containers	✅ Passed	Only go.mod changed; no manifests, Helm templates, or Dockerfiles were modified, so no CWE-250/CWE-266 privileged-container settings were introduced.
No Pii Or Sensitive Data In Logs	✅ Passed	Only go.mod changed; no slog/logr/zap/fmt logging code was added or modified, so no CWE-532 log leakage exposure is present.
Title check	✅ Passed	The title accurately describes the Go dependency upgrade from backoff v4.3.0 to v7.0.0.
Description check	✅ Passed	The description matches the changeset and documents the dependency version bump.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch konflux/mintmaker/main/github.com-cenkalti-backoff-v4-7.x

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch konflux/mintmaker/main/github.com-cenkalti-backoff-v4-7.x

---

_{Comment @coderabbitai help to get the list of available commands.}

[rafabene]

/ok-to-test

[hyperfleet-ci-bot]

Risk Score: 0 — risk/low

Signal	Detail	Points
PR size	2 lines	+0
Sensitive paths	none	+0

_{Computed by hyperfleet-risk-scorer}

[rafabene]

Closing — backoff v7 is a major version bump with breaking API changes (lint fails). Needs a dedicated ticket with code changes.

[rafabene]

/ok-to-test

[openshift-ci]

@red-hat-konflux-kflux-prd-rh02[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/lint	b90031b	link	true	/test lint

Full PR test history. Your PR dashboard.

Details

Instructions 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. I understand the commands that are listed here.