Repository navigation
Update Go Dependencies - #72
Open
red-hat-konflux[bot] wants to merge 1 commit into
Open
red-hat-konflux[bot] wants to merge 1 commit into
red-hat-konflux[bot] wants to merge 1 commit into
Conversation
red-hat-konflux
Bot
force-pushed
the
konflux/mintmaker/tech-preview/go-deps
branch
12 times, most recently
from
March 30, 2026 14:45
c4a6a07 to
09df490
Compare
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/tech-preview/go-deps
branch
12 times, most recently
from
April 4, 2026 14:35
e5537f5 to
ac8b4fa
Compare
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Due to Go's usage of Minimal Version Selection (MVS), these packages have been updated to the minimum version available, so will still abide by Details:
|
red-hat-konflux
Bot
force-pushed
the
konflux/mintmaker/tech-preview/go-deps
branch
3 times, most recently
from
April 5, 2026 02:30
e98e645 to
87ce976
Compare
red-hat-konflux
Bot
force-pushed
the
konflux/mintmaker/tech-preview/go-deps
branch
29 times, most recently
from
April 14, 2026 11:37
6baa790 to
0356203
Compare
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
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
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:
v1.4.2→v1.4.4v2.22.0→v2.34.0v1.36.1→v1.44.0v1.19.1→v1.25.0v0.6.1→v0.6.3v0.55.0→v0.73.1v0.74.0v1.9.0→v1.12.1v0.7.0→v0.16.0v0.32.1→v0.37.2v0.32.1→v0.37.2v0.32.1→v0.37.2v2.130.1→v2.140.0v0.20.4→v0.25.2Release Notes
go-logr/logr (github.com/go-logr/logr)
v1.4.4Compare Source
What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.4.3...v1.4.4
v1.4.3Compare Source
Minor release.
What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.4.2...v1.4.3
onsi/ginkgo (github.com/onsi/ginkgo/v2)
v2.34.0Compare Source
Features
DeferOnFailureregisters a callback that runs only when a spec fails - as soon as the failing node returns and before any teardown (JustAfterEach,AfterEach,AfterAll,DeferCleanup) - so it can capture the state teardown is about to destroy. It takes exactly whatDeferCleanuptakes and shares its scoping: called inBeforeEach/JustBeforeEach/Itit covers the spec, inBeforeAllthe ordered container, and inBeforeSuitethe whole suite. It is also available onGinkgoT(); note that this adds a method toFullGinkgoTInterface, so hand-written implementations of that interface need to add it. See https://onsi.github.io/ginkgo/#capturing-failure-state-deferonfailureFixes
AttachProgressReporter) are no longer called while Ginkgo holds an internal lock, so a reporter that callsCurrentSpecReport()orAddReportEntry()no longer stalls for 5 seconds and has its output dropped.--sleep-on-failurenow runs after anyDeferOnFailurecallbacks, also pauses when a spec times out, and no longer pauses if the suite has already been interrupted.v2.33.1Compare Source
Fixes
v2.33.0Compare Source
Features
ReportEntrys as<properties>on its<testcase>element, with the entry's name and its JSON-encoded value. Thanks @pohly! [23db51a]Maintenance
## Unreleasedas the work happens. See RELEASING.md. [8616ecb]v2.32.2Compare Source
2.32.2
Fixes
c6792b0]v2.32.1Compare Source
2.32.1
Fixes
e647b3b]v2.32.0Compare Source
2.32.0
-fdgenerate RSpec-style documentation output. Thank @woodie !--sleep-on-failure pauses a failed spec before teardown. Thanks @qinqon !
v2.31.0Compare Source
2.31.0
Add a bunch of Claude Skills via the marketplace:
v2.30.0Compare Source
2.30.0
Features
Ginkgo now allows
extentions/global.Resetto support running multiple suites from within a single process. This may take some massaging on your part (see 1672) but can dramatically speed up codebases with O(hundreds) of test suites.Thanks @lawrencejones !
Fixes
4f62d7a]v2.29.0Compare Source
2.29.0
GinkgoHelperGomakes it easier to write test helpers that need to run in goroutines. Specifically, it makes managing the failure state and capturing failure panics correctly straightforward.ginkgo outlinenow includes entries defined inDescribeTableSubtreev2.28.3Compare Source
2.28.3
Maintenance
Bump all dependencies
v2.28.2Compare Source
2.28.2
f3a36b6]94151c8]4d21dbb]c102161]9619647]5779304]v2.28.1Compare Source
2.28.1
Update all dependencies. This auto-updated the required version of Go to 1.24, consistent with the fact that Go 1.23 has been out of support for almost six months.
v2.28.0Compare Source
2.28.0
Ginkgo's SemVer filter now supports filtering multiple components by SemVer version:
can be filtered in or out with an invocation like:
ginkgo --sem-ver-filter="2.1.1, redis=8.2.0"Huge thanks to @Icarus9913 for working on this!
v2.27.5Compare Source
2.27.5
Fixes
Don't make a new formatter for each GinkgoT(); that's just silly and uses precious memory
v2.27.4Compare Source
2.27.4
Fixes
59bc751]v2.27.3Compare Source
2.27.3
Fixes
report exit result in case of failure [
1c9f356]fix data race [
ece19c8]v2.27.2Compare Source
2.27.2
Fixes
a69113a]Maintenance
a99c6e0]f993df5]v2.27.1Compare Source
2.27.1
Fixes
606c1cb]a6463b3]v2.27.0Compare Source
2.27.0
Features
Transforming Nodes during Tree Construction
This release adds support for
NodeArgsTransformers that can be registered withAddTreeConstructionNodeArgsTransformer.These are called during the tree construction phase as nodes are constructed and can modify the node strings and decorators. This enables frameworks built on top of Ginkgo to modify Ginkgo nodes and enforce conventions.
Learn more here.
Spec Prioritization
A new
SpecPriority(int)decorator has been added. Ginkgo will honor priority when ordering specs, ensuring that higher priority specs start running before lower priority specsLearn more here.
Maintenance
1333dae]17ae63e]v2.26.0Compare Source
2.26.0
Features
Ginkgo can now generate json-formatted reports that are compatible with the
go testjson format. Useginkgo --gojson-report=report.go.json. This is not intended to be a replacement for Ginkgo's native json format which is more information rich and better models Ginkgo's test structure semantics.v2.25.3Compare Source
2.25.3
Fixes
f01aed1]v2.25.2Compare Source
2.25.2
Fixes
Add github output group for progress report content
Maintenance
Bump Gomega
v2.25.1Compare Source
2.25.1
Fixes
10866d3]2e42cff]v2.25.0Compare Source
2.25.0
AroundNodeThis release introduces a new decorator to support more complex spec setup usecases.
AroundNoderegisters a function that runs before each individual node. This is considered a more advanced decorator.Please read the docs for more information and some examples.
Allowed signatures:
AroundNode(func())-funcwill be called before the node is run.AroundNode(func(ctx context.Context) context.Context)-funccan wrap the passed in context and return a new one which will be passed on to the node.AroundNode(func(ctx context.Context, body func(ctx context.Context)))-ctxis the context for the node andbodyis a function that must be called to run the node. This gives you complete control over what runs before and after the node.Multiple
AroundNodedecorators can be applied to a single node and they will run in the order they are applied.Unlike setup nodes like
BeforeEachandDeferCleanup,AroundNodeis guaranteed to run in the same goroutine as the decorated node. This is necessary when working with lower-level libraries that must run on a single thread (you can callruntime.LockOSThread()in theAroundNodeto ensure that the node runs on a single thread).Since
AroundNodeallows you to modify the context you can also useAroundNodeto implement shared setup that attaches values to the context.If applied to a container,
AroundNodewill run before every node in the container. Including setup nodes likeBeforeEachandDeferCleanup.AroundNodecan also be applied toRunSpecsto run before every node in the suite. This opens up new mechanisms for instrumenting individual nodes across an entire suite.v2.24.0Compare Source
2.24.0
Features
Specs can now be decorated with (e.g.)
SemVerConstraint("2.1.0")andginkgo --sem-ver-filter="2.1.1"will only run constrained specs that match the requested version. Learn more in the docs here! Thanks to @Icarus9913 for the PR.Fixes
3f5d379]. fixes #1582Maintenance
Numerous dependency bumps and documentation fixes
v2.23.4Compare Source
2.23.4
Prior to this release Ginkgo would compute the incorrect number of available CPUs when running with
-pin a linux container. Thanks to @emirot for the fix!Features
2b9c428]Fixes
1f59d07]Maintenance
2d134d5]v2.23.3Compare Source
2.23.3
Fixes
-as a standalone argument [cfcc1a5]feaf292]88e2282]v2.23.2Compare Source
2.23.2
🎉🎉🎉
At long last, some long-standing performance gaps between
ginkgoandgo testhave been resolved!Ginkgo operates by running
go test -cto generate test binaries, and then running those binaries. It turns out that the compilation step ofgo test -cis slower thango test's compilation step becausego teststrips out debug symbols (ldflags=-w) whereasgo test -cdoes not.Ginkgo now passes the appropriate
ldflagstogo test -cwhen running specs to strip out symbols. This is only done when it is safe to do so and symbols are preferred when profiling is enabled and whenginkgo buildis called explicitly.This, coupled, with the instructions for disabling XProtect on MacOS yields a much better performance experience with Ginkgo.
v2.23.1Compare Source
2.23.1
🚨 For users on MacOS 🚨
A long-standing Ginkgo performance issue on MacOS seems to be due to mac's antimalware XProtect. You can follow the instructions here to disable it in your terminal. Doing so sped up Ginkgo's own test suite from 1m8s to 47s.
Fixes
Ginkgo's CLI is now a bit clearer if you pass flags in incorrectly:
a0e52ff]b799d8d]This might cause existing CI builds to fail. If so then it's likely that your CI build was misconfigured and should be corrected. Open an issue if you need help.
v2.23.0Compare Source
2.23.0
Ginkgo 2.23.0 adds a handful of methods to
GinkgoT()to make it compatible with thetesting.TBinterface in Go 1.24.GinkgoT().Context(), in particular, is a useful shorthand for generating a new context that will clean itself up in aDeferCleanup(). This has subtle behavior differences from the golang implementation but should make sense in a Ginkgo... um... context.Features
37a511b]Fixes
7556a86]4df06c6]Maintenance
cbcf39a]9b261ff]00f19c8]e98a4df]60cc4e2]fea6f2d]31d7813]fc3bbd6]aee0d56]809a710]v2.22.2Compare Source
What's Changed
Full Changelog: onsi/ginkgo@v2.22.1...v2.22.2
v2.22.1Compare Source
2.22.1
Fixes
Fix CSV encoding
aab3da6]c09df39]96a80fc]43dad69]Maintenance
c88c634]4df44bf]onsi/gomega (github.com/onsi/gomega)
v1.44.0Compare Source
Fixes
BeNumericallycompares signed and unsigned integers by value:-1no longer equalsuint64(math.MaxUint64)anduint(5)is now greater than-3(#925) [26e3c6b]BeNumerically("~")no longer overflows when computing the distance between extreme integers (#928) [1955764]BeNumerically("==", x, threshold)now honors the threshold for floats, as it already did for integers (#927) [10e2aca]HaveKeyWithValuesucceeds if any key accepted by the key matcher has a matching value, rather than depending on map iteration order (#929) [ffc577a]HaveKeyandHaveKeyWithValuetreat key and value matcher errors likeContainElementdoes: a match wins, and an error is only reported when nothing matches (#926) [dc91598]MatchJSONno longer treats numbers too large for a float64 as equal to one another (#930) [9d619a5]MatchJSONcompares integers beyond ±2^53 exactly, so neighboring large integers (e.g. IDs) no longer match; all other numbers are still compared as float64s (#931) [8ef1aa7,630fe12]HaveExactElementsreports missing or extra elements that start at index 0, and reports the first extra element's index rather than the last (#934) [af1b777]MatchYAMLcompares every document in a multi-document stream rather than only the first; empty documents (e.g. a leading or trailing---) are ignored (#933) [2773796]MatchXMLignores namespace prefixes: elements and attributes are compared by namespace URI, and the URIs declared on each element must match whatever prefix they are bound to (#932) [c0dbd89,2565350]v1.43.1Compare Source
Maintenance
d547015]## Unreleasedas the work happens. Releases still ship the stripped-down tree onmaster-lite- tests removed and Ginkgo dropped fromgo.mod- and the workflow now builds it and checks it on every push. See RELEASING.md. [e9dc84d]v1.43.0Compare Source
1.43.0
Features
Add gomock adaptor extension for using Gomega matchers with gomock
v1.42.1Compare Source
1.42.1
Bump Dependencies
v1.42.0Compare Source
1.42.0
Add a set of Claude skill as a marketplace plugin
v1.41.0Compare Source
v1.40.0Compare Source
1.40.0
We're adopting a new release strategy to minimize dependency bloat in projects that consume Gomega. It is a limitation of the go mod toolchain that test subdependencies of your project's direct dependencies get pulled in as indirect dependencies. In the case of Gomega, this ends up pulling in all of Ginkgo into your
go.modeven if you are only using Gomega (Gomega uses Ginkgo for its own tests).Going forward, releases will strip out all tests, tidy up the
go.modand then push this stripped down version to a newmaster-litebranch. These stripped-down versions will receive thevx.y.zgit tag and will be picked up by the go toolchain.Please open an issue if this new release process causes unexpected changes for your projects.
v1.39.1Compare Source
1.39.1
Update all dependencies. This auto-updated the required version of Go to 1.24, consistent with the fact that Go 1.23 has been out of support for almost six months.
v1.39.0Compare Source
1.39.0
Features
Add
MatchErrorStrictlywhich only passes iferrors.Is(actual, expected)returns true.MatchError, by contrast, will fallback to string comparison.v1.38.3Compare Source
1.38.3
Fixes
make string formatitng more consistent for users who use format.Object directly
v1.38.2Compare Source
1.38.2
c404969]v1.38.1Compare Source
1.38.1
Fixes
Numerous minor fixes and dependency bumps
v1.38.0Compare Source
1.38.0
Features
4ee7ed0]Fixes
36bbf72]Maintenance
529d408]acd1f55]bae65a0]8dda91f]212d812]59bd7f9]328c729]9a798a1]04a72c6]v1.37.0Compare Source
1.37.0
Features
5666f98]v1.36.3Compare Source
1.36.3
Maintenance
adb8b49]interface{}withany[7613216]9fe5259]a0e85b9]604a8b1]36fbc84]ced70d7]c8b4a07]06431b9]b55a92d]a1d518b]v1.36.2Compare Source
Maintenance
prometheus/client_golang (github.com/prometheus/client_golang)
v1.25.0Compare Source
api/prometheus/v1(see the [CHANGE] entries below).1.25.0 / 2026-10-07
Query,QueryRange,Series,LabelNames, andLabelValuesnow returnInfosannotations in addition toWarnings, matching the Prometheus server's info annotations. This changes the signatures of these methods and ofapi.Client'sDo/DoGetFallback; custom API client implementations must be updated. #1963TSDBBlocksresult types to align with the Prometheus server'stsdb.BlockMeta:TSDBBlocksResultnow containsBlocks []TSDBBlockMetadirectly instead of mirroring the full API envelope, nested types are renamed (TSDBBlockMeta,TSDBBlockStats,TSDBBlockMetaCompaction), stat fields areuint64withomitemptytags, and the optional compactionparentsfield is included. #1928GatherAndFormatto encode a subset of metrics from a Gatherer. #2091HandlerOpts.AcceptedFormatsto customize the formats negotiated from the incomingAcceptheader, enabling opt-in to experimental formats such as OpenMetrics 2.0 without changing default negotiation. #2146Varyheader. #2142GatherAndFormatandCollectAndFormat(terminating# EOF). #2125:fooargument no longer substitutes inside:foobar. #2136What's changed
What's Changed
New Contributors
Configuration
📅 Schedule: (UTC)
🚦 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.Documentation
Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.