fix(deps): update go patch dependencies#242
Merged
Merged
Conversation
Contributor
|
/retest |
red-hat-konflux
Bot
force-pushed
the
konflux/mintmaker/main/go-patch-dependencies
branch
3 times, most recently
from
337ab1c to
2d372f8
Compare
red-hat-konflux
Bot
changed the title
red-hat-konflux
Bot
force-pushed
the
konflux/mintmaker/main/go-patch-dependencies
branch
from
2d372f8 to
d98ffd3
Compare
red-hat-konflux
Bot
changed the title
red-hat-konflux
Bot
force-pushed
the
konflux/mintmaker/main/go-patch-dependencies
branch
2 times, most recently
from
8e885d0 to
31f0c07
Compare
Contributor
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
red-hat-konflux
Bot
force-pushed
the
konflux/mintmaker/main/go-patch-dependencies
branch
7 times, most recently
from
83a35b3 to
ea7955f
Compare
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
red-hat-konflux
Bot
force-pushed
the
konflux/mintmaker/main/go-patch-dependencies
branch
from
ea7955f to
6c11c6e
Compare
MartinBasti
approved these changes
Nov 3, 2025
red-hat-konflux
Bot
deleted the
konflux/mintmaker/main/go-patch-dependencies
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v4.13.0->v4.13.1v5.9.0->v5.9.11v0.3.6->v0.3.16v0.6.1->v0.6.2v1.0.5->v1.0.10v3.5.0->v3.5.2Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Release Notes
antlr4-go/antlr (github.com/antlr4-go/antlr/v4)
v4.13.1: Release 4.13.1Compare Source
The 4.13.1 release has:
using mutexes, when the user knows they will not use it with multiple
go routines. (Note, somewhat experimental)
Note that I did not remove the sort.Slices calls. They will not be experimental for long
and are implemented efficently. Please make a fork if you must use it without this
dependency. Maybe review whether you need to do so for the sake of one call.
evanphx/json-patch (github.com/evanphx/json-patch/v5)
v5.9.11Compare Source
What's Changed
Full Changelog: evanphx/json-patch@v5.9.10...v5.9.11
v5.9.10Compare Source
What's Changed
New Contributors
Full Changelog: evanphx/json-patch@v5.9.0...v5.9.10
imdario/mergo (github.com/imdario/mergo)
v0.3.16: Announcement: v1.0.0 will be released on June 18thCompare 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 fixedCompare Source
v0.3.14: fix: Respect overwriteWithEmptySrc when merging maps #231Compare Source
v0.3.13: Merging same-type slices supported, YAML upgraded to v3 (only used in tests), and more flexibility for transformersCompare Source
What's Changed
New Contributors
Full Changelog: darccio/mergo@0.3.12...v0.3.13
v0.3.12: Some bug fixesCompare Source
Thanks to @abicky and @ndeloof to help to improve Mergo. They fixed issues #90 & #174.
v0.3.11Compare Source
v0.3.10: : frozen codebase + next stepsCompare 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 MapCompare Source
v0.3.8: Several PRs mergedCompare Source
v0.3.7Compare Source
Two PR merged to fix bugs. Thanks @requilence, @smgladkovskiy, @vdemeester and @luisdavim for your time!
prometheus/client_model (github.com/prometheus/client_model)
v0.6.2Compare Source
What's Changed
Full Changelog: prometheus/client_model@v0.6.1...v0.6.2
spf13/pflag (github.com/spf13/pflag)
v1.0.10Compare Source
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.9...v1.0.10
v1.0.9Compare Source
What's Changed
Full Changelog: spf13/pflag@v1.0.8...v1.0.9
v1.0.8Compare Source
This version, while only a patch bump, includes a (very minor) breaking change: the
flag.ParseErrorsWhiteliststruct and correspondingFlagSet.parseErrorsWhitelistfield have been renamed toParseErrorsAllowlist.This should result in compilation errors in any code that uses these fields, which can be fixed by adjusting the names at call sites. There is no change in semantics or behavior of the struct or field referred to by these names. If your code compiles without errors after bumping to/past v1.0.8, you are not affected by this change.
The breaking change was reverted in v1.0.9, by means of re-introducing the old names with deprecation warnings. The plan is still to remove them in a future release, so if your code does depend on the old names, please change them to use the new names at your earliest convenience.
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.7...v1.0.8
v1.0.7Compare Source
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.6...v1.0.7
v1.0.6Compare Source
What's Changed
pkg/flagcompatibility by @mckern in #220New Contributors
Full Changelog: spf13/pflag@v1.0.5...v1.0.6
gotestyourself/gotest.tools (gotest.tools/v3)
v3.5.2Compare Source
What's Changed
New Contributors
Full Changelog: gotestyourself/gotest.tools@v3.5.1...v3.5.2
v3.5.1Compare Source
What's Changed
New Contributors
Full Changelog: gotestyourself/gotest.tools@v3.5.0...v3.5.1
Configuration
📅 Schedule: 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
To execute skipped test pipelines write comment
/ok-to-test.This PR has been generated by MintMaker (powered by Renovate Bot).