chore(deps): update module github.com/imdario/mergo to v0.3.16

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

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/imdario/mergo	v0.3.6 → v0.3.16

---

Release Notes

imdario/mergo (github.com/imdario/mergo)

v0.3.16: Announcement: v1.0.0 will be released on June 18th

Compare Source

This release doesn't contain code changes.

After 10 years, with many corner cases covered, very few issues pending (at least, comparing them with the usage of the library as part of Docker, Kubernetes, Datadog's agent, etc.), and a very stable API, I think it's time to release a 1.0.0 version.

This version will be released under a vanity URL: dario.cat/mergo

PS: although I'll make sure that github.com/imdario/mergo will be available, I'm going to also change my GitHub handle, so expect for a few minutes to not be able to pull from github.com/imdario as I fork it from the new handle to the old one.

PS2: I'm creating a discussion for this release to make sure we can have a conversation around the topic, and anything else about Mergo that you care about.

v0.3.15: Issues #​131, #​170, #​220, and #​202 fixed

Compare Source

v0.3.14: fix: Respect overwriteWithEmptySrc when merging maps #​231

Compare Source

v0.3.13: Merging same-type slices supported, YAML upgraded to v3 (only used in tests), and more flexibility for transformers

Compare Source

What's Changed

• Fix typo in README.md by @​eltociear in #​184
• Adding StructBot to Mergo in the wild section by @​tjpnz in #​193
• Add Goreleaser to featured projects by @​marcauberer in #​191
• fix: gate transformers on valid non-nil destinations by @​zaquestion in #​211
• Support slices of same type by @​heaths in #​210
• Upgrade yaml to v3 by @​imdario in #​212

New Contributors

• @​eltociear made their first contribution in #​184
• @​tjpnz made their first contribution in #​193
• @​marcauberer made their first contribution in #​191
• @​zaquestion made their first contribution in #​211
• @​heaths made their first contribution in #​210

Full Changelog: darccio/mergo@0.3.12...v0.3.13

v0.3.12: Some bug fixes

Compare Source

Thanks to @​abicky and @​ndeloof to help to improve Mergo. They fixed issues #​90 & #​174.

v0.3.11

Compare Source

v0.3.10: : frozen codebase + next steps

Compare Source

After the broken 0.3.9, I decided to revert the faulty PR #​105, reopening the issues #​90 and #​103. Also, this release includes all the other pending bugs. As it is getting harder to modify the codebase, I decided to freeze it. I'm going to merge only PRs fixing bugs with proper tests.

On the other hand, I will start a new cleanroom implementation. Existing tests will be reviewed and used as "test subjects". Also, I plan to collect real-world examples to use them also as "test subjects" in a separate repository.

In this process, I would like to work from the bottom to the top, focusing on getting the core right. I plan to keep a legacy compatibility layer, but the new API may differ from the current one to allow better maintenance and new features.

v0.3.9: Support for Struct in Map

Compare Source

v0.3.8: Several PRs merged

Compare Source

v0.3.7

Compare Source

Two PR merged to fix bugs. Thanks @​requilence, @​smgladkovskiy, @​vdemeester and @​luisdavim for your time!

---

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.

[openshift-ci]

Hi @red-hat-konflux-kflux-prd-rh02[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.