chore(deps): update module gomodules.xyz/jsonpatch/v2 to v3

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

This PR contains the following updates:

Package	Change	Age	Confidence
gomodules.xyz/jsonpatch/v2	v2.5.0 → v3.0.1

---

Release Notes

gomodules/jsonpatch (gomodules.xyz/jsonpatch/v2)

v3.0.1

Compare Source

This release uses our forked gomodules/orderedmap library. Our forked version has 2 major changes:

• Uses *OrderedMap instead of OrderedMap inside nested orderedmaps.
• I ported unstructured helpers from Kubernetes to work with orderedmaps.

v3.0.0

Compare Source

This release uses iancoleman/orderedmap to generate predictable patch. This is very useful if the generated patch is checked into a VCS like git.

---

Configuration

📅 Schedule: (in timezone UTC)

• Branch creation
  • Between 02:00 AM and 04:59 AM, Monday through Friday (* 2-4 * * 1-5)
• 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.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 65.60%. Comparing base (a90f853) to head (ab5d99f).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #294   +/-   ##
=======================================
  Coverage   65.60%   65.60%           
=======================================
  Files          23       23           
  Lines        1608     1608           
=======================================
  Hits         1055     1055           
  Misses        473      473           
  Partials       80       80           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[openshift-ci]

Hi @red-hat-konflux-kflux-prd-rh03[bot]. Thanks for your PR.

I'm waiting for a openshift 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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux-kflux-prd-rh03[bot]
Once this PR has been reviewed and has the lgtm label, please assign charlesgong 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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux-kflux-prd-rh03[bot]
Once this PR has been reviewed and has the lgtm label, please assign charlesgong 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

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 12:06 PM UTC · Completed 12:14 PM UTC

Commit: 250b1da · View workflow run →

[fullsend-ai-retro]

Retro Analysis: PR #294

PR: #294 — chore(deps): update module gomodules.xyz/jsonpatch/v2 to v3 - autoclosed

What happened

This was an automated dependency update PR created by the MintMaker/Renovate bot on 2026-06-16. It proposed updating gomodules.xyz/jsonpatch/v2, went through 3 close/reopen cycles over ~2 months, failed CI checks (ci/prow/lint, ci/prow/validate), received zero human reviews or comments, and was autoclosed on 2026-08-14 without merging.

No fullsend agents (review, code, triage, fix, prioritize) were ever dispatched for this PR. The only agent triggered was the retro agent, fired automatically by the PR close event. The routing logic for retro on PR close is intentionally ungated per ADR 0054 — any PR closure triggers retro regardless of author, merge status, or prior agent involvement.

Assessment

This retro run produced no actionable findings because there was no agent workflow to analyze — no agents interacted with the PR, and no humans reviewed it. The token cost of running a full retro analysis on a zero-interaction bot dependency PR is pure waste.

Existing coverage

This is a well-known and heavily-tracked problem. There are 30+ open issues in fullsend-ai/fullsend proposing various forms of retro/agent skip logic for bot-authored and zero-interaction PRs. The consolidation issue fullsend-ai/fullsend#5817 tracks all of them. The most directly relevant existing issues:

• #5943 — Skip retro dispatch for any unmerged PR with zero fullsend agent involvement
• #4006 — Skip retro stage for automated dependency PRs (Renovate, Dependabot, MintMaker)
• #5619 — Broaden retro skip criteria to all unmerged PRs with no agent interaction
• #6205 — Bot-login constants use REST-style [bot] suffix that never matches GraphQL-sourced logins (a root cause for why bot detection may not work)
• #6007 — Agent guard misidentifies GitHub App bot PRs as human-authored

This retro run itself is evidence that the problem persists: a zero-interaction autoclosed Renovate PR still triggers a full retro analysis. No new proposals are warranted — the existing issue set comprehensively covers the needed improvements.

No proposals filed

All improvement opportunities identified in this retro are already covered by existing open issues. Filing additional proposals would add to the duplication that #5817 is trying to consolidate.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Advanced

Run ID: 889101e8-c677-4c6f-89d9-34ce419a7736

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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

[openshift-ci]

@red-hat-konflux-kflux-prd-rh03[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/validate	ab5d99f	link	true	/test validate

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.