Update all non-major dependencies - #223
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
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:
|
|
|
renovate
Bot
force-pushed
the
renovate/all-non-major
branch
from
August 7, 2026 23:14
b8cceb0 to
275f7f9
Compare
renovate
Bot
force-pushed
the
renovate/all-non-major
branch
2 times, most recently
from
August 21, 2026 00:07
a9abb3f to
4ca4b16
Compare
renovate
Bot
force-pushed
the
renovate/all-non-major
branch
2 times, most recently
from
September 1, 2026 06:20
b32db2a to
3cf09a4
Compare
renovate
Bot
force-pushed
the
renovate/all-non-major
branch
from
September 6, 2026 00:11
3cf09a4 to
c78229f
Compare
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:
1.19→1.251.27(+1)15.5.1→15.14.0v0.3.0→v0.3.4v1.2.3→v1.4.4v2.7.0→v2.32.1v1.25.0→v1.43.0v1.8.1→v1.12.1v2.15.4→v2.18.0v2.18.1v0.26.0→v0.37.0v0.26.0→v0.37.0v0.26.0→v0.37.0v0.14.1→v0.24.1v0.25.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
fairwindsops/controller-utils (github.com/fairwindsops/controller-utils)
v0.3.4Compare Source
Changelog
745f869Added Controller validation (#102)8d57777Managed by Terraform149357cUpdated staticcheck@2023.1.7 (#103)v0.3.3Compare Source
Changelog
047baa9Update_API_GoClient_APImachinery (#90)v0.3.2Compare Source
Changelog
984bb05Bump github.com/stretchr/testify from 1.8.0 to 1.8.4 (#76)3185c7fFWI-4610 - /vv/add pod metadata support (#80)v0.3.1Compare Source
Changelog
e2eecfaAddGetAllPersistentVolumeClaimsto return all PVCs as unstructured objects (#63)cdb4da7Remove the changelog in favor of goreleaser (#64)6455721Set log level (#58)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
v1.4.2Compare Source
What's Changed
Dependencies:
Full Changelog: go-logr/logr@v1.4.1...v1.4.2
v1.4.1Compare Source
What's Changed
Full Changelog: go-logr/logr@v1.4.0...v1.4.1
v1.4.0Compare Source
This release dramatically improves interoperability with Go's
log/slogpackage. In particular,logr.NewContextandlogr.NewContextWithSlogLoggeruse the same context key, which allowslogr.FromContextandlogr.FromContextAsSlogLoggerto returnlogr.Loggeror*slog.Loggerrespectively, including transparently converting each to the other as needed.Functions
logr/slogr.NewLograndlogr/slogr.ToSlogHandlerhave been superceded bylogr.FromSlogHandlerandlogr.ToSlogHandlerrespectively, and typelogr/slogr.SlogSinkhas been superceded bylogr.SlogSink. All of the old names inlogr/slogrremain, for compatibility.Package
logr/funcrnow supportslogr.SlogSink, meaning that it's output passes all but one of the Slog conformance tests (that exception being thatfuncrhandles the timestamp itself).Users who have a
logr.Loggerand need a*slog.Loggercan callslog.New(logr.ToSlogHandler(...))and all output will go through the same stack.Users who have a
*slog.Loggerorslog.Handlercan calllogr.FromSlogHandler(...)and all output will go through the same stack.What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.3.0...v1.4.0
v1.3.0Compare Source
This release adds support for slog in a new, self-contained
logr/slogrpackage. Implementers of alogr.LogSinkare encouraged, but not required, to extend their implementation to improve the quality of log output coming from aslogAPI call.Breaking change: the call depth for
LogSink.Enabledwhen called viaLogger.Enabledwas fixed to be the same as for other call paths. Implementers of aLogSinkwho have worked around this bug will need to remove their workarounds.Security best practices were improved. Only Go versions >= 1.18 are supported by this release.
What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.2.4...v1.3.0
v1.2.4Compare Source
This is a collection of small bugfixes and documentation updates.
NOTE: A change (#166) which was thought to be compatible seems to be a breaking change. In particular, one used to be able to differentiate the result of
Discard()fromLogger{}. After this change, those are the same. We are considering how to address this, but do not currently plan to revert this change. Apologies!What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.2.3...v1.2.4
onsi/ginkgo (github.com/onsi/ginkgo/v2)
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]v2.22.0Compare Source
2.22.0
Features
0fcaa08]This allows serial tests to be filtered using the
label-filterMaintenance
Various doc fixes
v2.21.0Compare Source
2.21.0
Features
a69eb39]bcab9c8]Fixes
e548367]SpecsThatWillBeRunwithSpecsThatWillRun[
c2c4d3c]Maintenance
7e65a00]v2.20.2Compare Source
2.20.2
Require Go 1.22+
Maintenance
a671816]v2.20.1Compare Source
2.20.1
Fixes
d6f9640]v2.20.0Compare Source
2.20.0
Features
be5ab95]Maintenance
d303d14]7a50221]v2.19.1Compare Source
2.19.1
Fixes
63c8c30]ff41e27]Maintenance
76f4e0c]b69c00d]f097741]v2.19.0Compare Source
2.19.0
Features
Label Sets allow for more expressive and flexible label filtering.
v2.18.0Compare Source
2.18.0
Features
f010b65]d80eebe]Fixes
42013d6]Maintenance
fcf1fd7]8bb14fd]04bfad7]v2.17.3Compare Source
2.17.3
Fixes
ginkgo watchnow ignores hidden files [bde6e00]v2.17.2Compare Source
2.17.2
Fixes
32259c8]780e7a3]Maintenance
d91fe4e]8cb662e]3134422]eca81b4]760def8](https://redirect.github.com/onsiConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.