fix(deps): update go modules (major)

[red-hat-konflux]

This PR contains the following updates:

Package	Type	Update	Change
github.com/cenkalti/backoff/v4	indirect	major	v4.3.0 -> v5.0.2
gomodules.xyz/jsonpatch/v2	indirect	major	v2.5.0 -> v3.0.1
gopkg.in/evanphx/json-patch.v4	indirect	major	v4.12.0 -> v5.9.11
gopkg.in/yaml.v2	require	major	v2.4.0 -> v3.0.1
sigs.k8s.io/structured-merge-diff/v4	indirect	major	v4.7.0 -> v6.0.0

---

Warning

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

---

Release Notes

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

v5.0.2

Compare Source

v5.0.1

Compare Source

v5.0.0

Compare Source

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.

evanphx/json-patch (gopkg.in/evanphx/json-patch.v4)

v5.9.11

Compare Source

What's Changed

• Export errBadJSONDoc and errBadJSONPatch errors by @​skitt in https://github.com/evanphx/json-patch/pull/209

Full Changelog: evanphx/json-patch@v5.9.10...v5.9.11

v5.9.10

Compare Source

What's Changed

• Drop the reference to gopkg.in for v5 by @​skitt in https://github.com/evanphx/json-patch/pull/203
• remove unmaintained errors pkg(github.com/pkg/errors) by @​koba1t in https://github.com/evanphx/json-patch/pull/206

New Contributors

• @​skitt made their first contribution in https://github.com/evanphx/json-patch/pull/203
• @​koba1t made their first contribution in https://github.com/evanphx/json-patch/pull/206

Full Changelog: evanphx/json-patch@v5.9.0...v5.9.10

v5.9.0

Compare Source

What's Changed

• Validate that the partialDoc is decoded correctly by @​evanphx in https://github.com/evanphx/json-patch/pull/201
• Add option to control if the output is HTMLEscaped by @​evanphx in https://github.com/evanphx/json-patch/pull/202

Full Changelog: evanphx/json-patch@v5.8.1...v5.9.0

v5.8.1: Fix API breakage

Compare Source

This PR fixes Operation containing a reference to internal/json and breaking the ability to manually compose one. This restores that ability using a type alias.

Full Changelog: evanphx/json-patch@v5.8.0...v5.8.1

v5.8.0: Blargh Phixs and Empathyprovements

Compare Source

This release fixes a few stray panics, addresses large number accuracy, and improves performance!

What's Changed

• Compare strings after decoding them to handle unicode correctly. Fixes #​172 by @​evanphx in https://github.com/evanphx/json-patch/pull/195
• Always use UseNumber() to avoid float64 lossyness by @​evanphx in https://github.com/evanphx/json-patch/pull/194
• Handle null correctly when introduced by replace. Fixes #​171 by @​evanphx in https://github.com/evanphx/json-patch/pull/196
• Handle from="" more properly. Fixes #​192 by @​evanphx in https://github.com/evanphx/json-patch/pull/193
• Improve performance by @​evanphx in https://github.com/evanphx/json-patch/pull/197

Full Changelog: evanphx/json-patch@v5.7.0...v5.8.0

v5.7.0: The 2023 Release

Compare Source

What's Changed

• Fix invalid sprintf by @​howardjohn in https://github.com/evanphx/json-patch/pull/152
• Add CIFuzz GitHub action by @​DavidKorczynski in https://github.com/evanphx/json-patch/pull/167
• README: Remove Travis by @​ohkinozomu in https://github.com/evanphx/json-patch/pull/164
• Updated min supported version to go 1.18 by @​Neo2308 in https://github.com/evanphx/json-patch/pull/181
• Added dependabot by @​Neo2308 in https://github.com/evanphx/json-patch/pull/182
• Pre-flight DecodePatch validation: Issue #​177 by @​radwaretaltr in https://github.com/evanphx/json-patch/pull/180
• Check if raw is a null pointer for findObject by @​JosieLi-Google in https://github.com/evanphx/json-patch/pull/173
• Bump actions/checkout from 2 to 4 by @​dependabot in https://github.com/evanphx/json-patch/pull/187
• Fix panic on test op by @​erickertz in https://github.com/evanphx/json-patch/pull/158

New Contributors

• @​howardjohn made their first contribution in https://github.com/evanphx/json-patch/pull/152
• @​DavidKorczynski made their first contribution in https://github.com/evanphx/json-patch/pull/167
• @​ohkinozomu made their first contribution in https://github.com/evanphx/json-patch/pull/164
• @​Neo2308 made their first contribution in https://github.com/evanphx/json-patch/pull/181
• @​radwaretaltr made their first contribution in https://github.com/evanphx/json-patch/pull/180
• @​JosieLi-Google made their first contribution in https://github.com/evanphx/json-patch/pull/173
• @​dependabot made their first contribution in https://github.com/evanphx/json-patch/pull/187
• @​erickertz made their first contribution in https://github.com/evanphx/json-patch/pull/158

Full Changelog: evanphx/json-patch@v5.6.0...v5.7.0

v5.6.0: Bug fixes

Compare Source

What's Changed

• Function ensurePathExists should handle appending correctly by @​MarcelMue in https://github.com/evanphx/json-patch/pull/148
• Fix partial negative indice support in v4 by @​zqzten in https://github.com/evanphx/json-patch/pull/146

New Contributors

• @​MarcelMue made their first contribution in https://github.com/evanphx/json-patch/pull/148
• @​zqzten made their first contribution in https://github.com/evanphx/json-patch/pull/146

Full Changelog: evanphx/json-patch@v5.5.0...v5.6.0

v5.5.0: Better null handling

Compare Source

This incorporates a few fixes related to how nulls are handles in array's and objects.

v5.3.0: Fix zero sized document crash

Compare Source

This fixes a crash bug where submitted an empty slice as the document would panic.

v5.2.0

Compare Source

v5.1.0

Compare Source

v5.0.0: Proper Go modules release

Compare Source

This release has a proper /v5 directory, unlike the previous releases that did not have a /v4 dir. Thanks to @​BenTheElder for getting this sorted out!

go-yaml/yaml (gopkg.in/yaml.v2)

v3.0.1

Compare Source

v3.0.0

Compare Source

kubernetes-sigs/structured-merge-diff (sigs.k8s.io/structured-merge-diff/v4)

v6.0.0

Unexported value.ReadJSONIter and value.WriteJSONStream, which return json-iter types, to enable a migration away from json-iter, since it is unmaintained.

---

Configuration

📅 Schedule: Branch creation - "after 5am on sunday" (UTC), 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.

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

This PR has been generated by MintMaker (powered by Renovate Bot).

[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 oliviercazade for approval. For more information see the Code Review Process.

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

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[bot]. Thanks for your PR.

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

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.