Skip to content

fix(deps): update golang-dependencies - #22

Merged
renovate[bot] merged 1 commit into
development/130.0from
renovate/golang-dependencies
May 12, 2026
Merged

fix(deps): update golang-dependencies#22
renovate[bot] merged 1 commit into
development/130.0from
renovate/golang-dependencies

Conversation

@renovate

@renovate renovate Bot commented Jun 23, 2025 •
edited
Loading

Copy link
Copy Markdown

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
github.com/go-logr/logr v1.4.1 → v1.4.3 age confidence
github.com/onsi/ginkgo/v2 v2.17.1 → v2.28.3 age confidence
github.com/onsi/gomega v1.32.0 → v1.40.0 age confidence
github.com/stretchr/testify v1.8.4 → v1.11.1 age confidence
github.com/stretchr/testify v1.6.1 → v1.11.1 age confidence
gopkg.in/yaml.v2 v2.3.0 → v2.4.0 age confidence
k8s.io/api v0.30.1 → v0.36.0 age confidence
k8s.io/apimachinery v0.30.1 → v0.36.0 age confidence
k8s.io/client-go v0.30.1 → v0.36.0 age confidence
sigs.k8s.io/controller-runtime v0.18.4 → v0.24.1 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

go-logr/logr (github.com/go-logr/logr)

v1.4.3

Compare Source

Minor release.

What's Changed

New Contributors

Full Changelog: go-logr/logr@v1.4.2...v1.4.3

v1.4.2

Compare Source

What's Changed

Dependencies:

Full Changelog: go-logr/logr@v1.4.1...v1.4.2

onsi/ginkgo (github.com/onsi/ginkgo/v2)

v2.28.3

Compare Source

2.28.3

Maintenance

Bump all dependencies

v2.28.2

Compare Source

2.28.2

  • Add ArtifactDir() to support Go 1.26 testing.TB interface [f3a36b6]
  • Implement shell completion [94151c8]
  • Add asan CLI option mirroring msan implementation [4d21dbb]
  • Bump uri from 1.0.3 to 1.0.4 in /docs (#​1630) [c102161]
  • fix aspect ratio [9619647]
  • update logos [5779304]

v2.28.1

Compare 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.0

Compare Source

2.28.0

Ginkgo's SemVer filter now supports filtering multiple components by SemVer version:

It("should work in a specific version range (1.0.0, 2.0.0) and third-party dependency redis in [8.0.0, ~)", SemVerConstraint(">= 3.2.0"), ComponentSemVerConstraint("redis", ">= 8.0.0") func() {
    // This test will only run when version is between 1.0.0 (exclusive) and 2.0.0 (exclusive) and redis version is >= 8.0.0
})

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

Compare Source

2.27.5

Fixes

Don't make a new formatter for each GinkgoT(); that's just silly and uses precious memory

v2.27.4

Compare Source

2.27.4

Fixes
  • CurrentTreeConstructionNodeReport: fix for nested container nodes [59bc751]

v2.27.3

Compare Source

2.27.3

Fixes

report exit result in case of failure [1c9f356]
fix data race [ece19c8]

v2.27.2

Compare Source

2.27.2

Fixes
  • inline automaxprocs to simplify dependencies; this will be removed when Go 1.26 comes out [a69113a]
Maintenance
  • Fix syntax errors and typo [a99c6e0]
  • Fix paragraph position error [f993df5]

v2.27.1

Compare Source

2.27.1

Fixes
  • Fix Ginkgo Reporter slice-bounds panic [606c1cb]
  • Bug Fix: Add GinkoTBWrapper.Attr() and GinkoTBWrapper.Output() [a6463b3]

v2.27.0

Compare Source

2.27.0

Features
Transforming Nodes during Tree Construction

This release adds support for NodeArgsTransformers that can be registered with AddTreeConstructionNodeArgsTransformer.

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 specs

Learn more here.

Maintenance

v2.26.0

Compare Source

2.26.0

Features

Ginkgo can now generate json-formatted reports that are compatible with the go test json format. Use ginkgo --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.3

Compare Source

2.25.3

Fixes
  • emit --github-output group only for progress report itself [f01aed1]

v2.25.2

Compare Source

2.25.2

Fixes

Add github output group for progress report content

Maintenance

Bump Gomega

v2.25.1

Compare Source

2.25.1

Fixes
  • fix(types): ignore nameless nodes on FullText() [10866d3]
  • chore: fix some CodeQL warnings [2e42cff]

v2.25.0

Compare Source

2.25.0

AroundNode

This release introduces a new decorator to support more complex spec setup usecases.

AroundNode registers 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()) - func will be called before the node is run.
  • AroundNode(func(ctx context.Context) context.Context) - func can 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))) - ctx is the context for the node and body is a function that must be called to run the node. This gives you complete control over what runs before and after the node.

Multiple AroundNode decorators can be applied to a single node and they will run in the order they are applied.

Unlike setup nodes like BeforeEach and DeferCleanup, AroundNode is 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 call runtime.LockOSThread() in the AroundNode to ensure that the node runs on a single thread).

Since AroundNode allows you to modify the context you can also use AroundNode to implement shared setup that attaches values to the context.

If applied to a container, AroundNode will run before every node in the container. Including setup nodes like BeforeEach and DeferCleanup.

AroundNode can also be applied to RunSpecs to run before every node in the suite. This opens up new mechanisms for instrumenting individual nodes across an entire suite.

v2.24.0

Compare Source

2.24.0

Features

Specs can now be decorated with (e.g.) SemVerConstraint("2.1.0") and ginkgo --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
Maintenance

Numerous dependency bumps and documentation fixes

v2.23.4

Compare Source

2.23.4

Prior to this release Ginkgo would compute the incorrect number of available CPUs when running with -p in a linux container. Thanks to @​emirot for the fix!

Features
  • Add automaxprocs for using CPUQuota [2b9c428]
Fixes
  • clarify gotchas about -vet flag [1f59d07]
Maintenance

v2.23.3

Compare Source

2.23.3

Fixes
  • allow - as a standalone argument [cfcc1a5]
  • Bug Fix: Add GinkoTBWrapper.Chdir() and GinkoTBWrapper.Context() [feaf292]
  • ignore exit code for symbol test on linux [88e2282]

v2.23.2

Compare Source

2.23.2

🎉🎉🎉

At long last, some long-standing performance gaps between ginkgo and go test have been resolved!

Ginkgo operates by running go test -c to generate test binaries, and then running those binaries. It turns out that the compilation step of go test -c is slower than go test's compilation step because go test strips out debug symbols (ldflags=-w) whereas go test -c does not.

Ginkgo now passes the appropriate ldflags to go test -c when 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 when ginkgo build is called explicitly.

This, coupled, with the instructions for disabling XProtect on MacOS yields a much better performance experience with Ginkgo.

v2.23.1

Compare 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:

  • make it clearer that you need to pass a filename to the various profile flags, not an absolute directory [a0e52ff]
  • emit an error and exit if the ginkgo invocation includes flags after positional arguments [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.0

Compare Source

2.23.0

Ginkgo 2.23.0 adds a handful of methods to GinkgoT() to make it compatible with the testing.TB interface in Go 1.24. GinkgoT().Context(), in particular, is a useful shorthand for generating a new context that will clean itself up in a DeferCleanup(). This has subtle behavior differences from the golang implementation but should make sense in a Ginkgo... um... context.

Features
  • bump to go 1.24.0 - support new testing.TB methods and add a test to cover testing.TB regressions [37a511b]
Fixes
  • fix edge case where build -o is pointing at an explicit file, not a directory [7556a86]
  • Fix binary paths when precompiling multiple suites. [4df06c6]
Maintenance

v2.22.2

Compare Source

What's Changed

Full Changelog: onsi/ginkgo@v2.22.1...v2.22.2

v2.22.1

Compare Source

2.22.1

Fixes

Fix CSV encoding

Maintenance
  • ensure *.test files are gitignored so we don't accidentally commit compiled tests again [c88c634]
  • remove golang.org/x/net/context in favour of stdlib context [4df44bf]

v2.22.0

Compare Source

2.22.0

Features
  • Add label to serial nodes [0fcaa08]

This allows serial tests to be filtered using the label-filter

Maintenance

Various doc fixes

v2.21.0

Compare Source

2.21.0

Features
  • add support for GINKGO_TIME_FORMAT [a69eb39]
  • add GINKGO_NO_COLOR to disable colors via environment variables [bcab9c8]
Fixes
  • increase threshold in timeline matcher [e548367]
  • Fix the document by replacing SpecsThatWillBeRun with SpecsThatWillRun
    [c2c4d3c]
Maintenance
  • bump various dependencies [7e65a00]

v2.20.2

Compare Source

2.20.2

Require Go 1.22+

Maintenance

v2.20.1

Compare Source

2.20.1

Fixes
  • make BeSpecEvent duration matcher more forgiving [d6f9640]

v2.20.0

Compare Source

2.20.0

Features
Maintenance
  • Add update-deps to makefile [d303d14]
  • bump all dependencies [7a50221]

v2.19.1

Compare Source

2.19.1

Fixes
  • update supported platforms for race conditions [63c8c30]
  • [build] Allow custom name for binaries. [ff41e27]
Maintenance

v2.19.0

Compare Source

2.19.0

Features

Label Sets allow for more expressive and flexible label filtering.

v2.18.0

Compare Source

2.18.0

Features
  • Add --slience-skips and --force-newlines [f010b65]
  • fail when no tests were run and --fail-on-empty was set [d80eebe]
Fixes
  • Fix table entry context edge case [42013d6]
Maintenance

v2.17.3

Compare Source

2.17.3

Fixes

ginkgo watch now ignores hidden files [bde6e00]

v2.17.2

Compare Source

2.17.2

Fixes
  • fix: close files [32259c8]
  • fix github output log level for skipped specs [780e7a3]
Maintenance
onsi/gomega (github.com/onsi/gomega)

v1.40.0

Compare 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.mod even 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.mod and then push this stripped down version to a new master-lite branch. These stripped-down versions will receive the vx.y.z git 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.1

Compare 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.0

Compare Source

1.39.0

Features

Add MatchErrorStrictly which only passes if errors.Is(actual, expected) returns true. MatchError, by contrast, will fallback to string comparison.

v1.38.3

Compare Source

1.38.3

Fixes

make string formatitng more consistent for users who use format.Object directly

v1.38.2

Compare Source

1.38.2

v1.38.1

Compare Source

1.38.1

Fixes

Numerous minor fixes and dependency bumps

v1.38.0

Compare Source

1.38.0

Features
  • gstruct handles extra unexported fields [4ee7ed0]
Fixes
  • support [] in IgnoringTopFunction function signatures (#​851) [36bbf72]
Maintenance

v1.37.0

Compare Source

1.37.0

Features
  • add To/ToNot/NotTo aliases for AsyncAssertion [5666f98]

v1.36.3

Compare Source

1.36.3

Maintenance

v1.36.2

Compare Source

Maintenance

v1.36.1

Compare Source

1.36.1
Fixes

v1.36.0

Compare Source

1.36.0

Features
  • new: make collection-related matchers Go 1.23 iterator aware [4c964c6]
Maintenance
  • Replace min/max helpers with built-in min/max [ece6872]
  • Fix some typos in docs [8e924d7]

v1.35.1

Compare Source

1.35.1

Fixes
  • Export EnforceDefaultTimeoutsWhenUsingContexts and DisableDefaultTimeoutsWhenUsingContext [ca36da1]

v1.35.0

Compare Source

1.35.0

Features
  • You can now call EnforceDefaultTimeoutsWhenUsingContexts() to have Eventually honor the default timeout when passed a context. (prior to this you had to expclility add a timeout) [e4c4265]
  • You can call StopTrying(message).Successfully() to abort a Consistently early without failure [eeca931]
Fixes
  • Stop memoizing the result of HaveField to avoid unexpected errors when used with async assertions. [3bdbc4e]
Maintenance

v1.34.2

Compare Source

1.34.2

Require Go 1.22+

Maintenance
  • bump ginkgo as well [c59c6dc]
  • bump to go 1.22 - remove x/exp dependency [8158b99]

v1.34.1

Compare Source

1.34.1

Maintenance
  • Use slices from exp/slices to keep golang 1.20 compat [5e71dcd]

v1.34.0

Compare Source

1.34.0

Features
  • Add RoundTripper method to ghttp.Server [c549e0d]
Fixes
  • fix incorrect handling of nil slices in HaveExactElements (fixes #​771) [878940c]
  • issue_765 - fixed bug in Hopcroft-Karp algorithm [ebadb67]
Maintenance

v1.33.1

Compare Source

1.33.1

Fixes
  • fix confusing eventually docs [3a66379]
Maintenance
  • Bump github.com/onsi/ginkgo/v2 from 2.17.1 to 2.17.2 [e9bc35a]

v1.33.0

Compare Source

1.33.0

Features

Receive not accepts Receive(<POINTER>, MATCHER>), allowing you to pick out a specific value on the channel that satisfies the provided matcher and is stored in the provided pointer.

Maintenance
stretchr/testify (github.com/stretchr/testify)

v1.11.1

Compare Source

This release fixes #​1785 introduced in v1.11.0 where expected argument values implementing the stringer interface (String() string) with a method which mutates their value, when passed to mock.Mock.On (m.On("Method", <expected>).Return()) or actual argument values passed to mock.Mock.Called may no longer match one another where they previously did match. The behaviour prior to v1.11.0 where the stringer is always called is restored. Future testify releases may not call the stringer method at all in this case.

What's Changed

Full Changelog: stretchr/testify@v1.11.0...v1.11.1

v1.11.0

Compare Source

What's Changed

Functional Changes

v1.11.0 Includes a number of performance improvements.

Fixes
Documentation, Build & CI

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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

  • If you want to rebase/retry this PR, check this box

@renovate

renovate Bot commented Jun 23, 2025 •
edited
Loading

Copy link
Copy Markdown
Author

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: storage-operator/go.mod
Post-upgrade command 'go mod tidy' has not been added to the allowed list in allowedCommands
File name: storage-operator/go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: operator/go.mod
Post-upgrade command 'go mod tidy' has not been added to the allowed list in allowedCommands
File name: operator/go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: storage-operator/go.mod
Post-upgrade command 'go mod tidy' has not been added to the allowed list in allowedCommands
File name: storage-operator/go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: operator/go.mod
Post-upgrade command 'go mod tidy' has not been added to the allowed list in allowedCommands
File name: operator/go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: storage-operator/go.mod
Post-upgrade command 'go mod tidy' has not been added to the allowed list in allowedCommands
File name: storage-operator/go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: operator/go.mod
Post-upgrade command 'go mod tidy' has not been added to the allowed list in allowedCommands
File name: operator/go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: storage-operator/go.mod
Post-upgrade command 'go mod tidy' has not been added to the allowed list in allowedCommands
File name: storage-operator/go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: go/solution-operator-lib/go.mod
Post-upgrade command 'go mod tidy' has not been added to the allowed list in allowedCommands
File name: go/solution-operator-lib/go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: go/solution-operator-lib/go.mod
Post-upgrade command 'go mod tidy' has not been added to the allowed list in allowedCommands
File name: go/solution-operator-lib/go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: storage-operator/go.mod
Post-upgrade command 'go mod tidy' has not been added to the allowed list in allowedCommands
File name: storage-operator/go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: operator/go.mod
Post-upgrade command 'go mod tidy' has not been added to the allowed list in allowedCommands
File name: operator/go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: storage-operator/go.mod
Post-upgrade command 'go mod tidy' has not been added to the allowed list in allowedCommands
File name: storage-operator/go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: operator/go.mod
Post-upgrade command 'go mod tidy' has not been added to the allowed list in allowedCommands
File name: operator/go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: storage-operator/go.mod
Post-upgrade command 'go mod tidy' has not been added to the allowed list in allowedCommands
File name: storage-operator/go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: operator/go.mod
Post-upgrade command 'go mod tidy' has not been added to the allowed list in allowedCommands
File name: operator/go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: storage-operator/go.mod
Post-upgrade command 'go mod tidy' has not been added to the allowed list in allowedCommands
File name: storage-operator/go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: operator/go.mod
Post-upgrade command 'go mod tidy' has not been added to the allowed list in allowedCommands
File name: operator/go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands

@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch 3 times, most recently from f5ee957 to 75b42ac Compare June 23, 2025 14:58
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch 2 times, most recently from 56136d8 to 3e03646 Compare July 16, 2025 12:48
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch 3 times, most recently from 152277f to 56a1ef7 Compare July 28, 2025 20:26
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch 3 times, most recently from f49ee66 to 71157d7 Compare August 10, 2025 00:39
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch 6 times, most recently from d5ce63f to 89d4cee Compare August 21, 2025 05:26
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch 7 times, most recently from 340b5f7 to fa0f5a6 Compare August 28, 2025 07:15
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch 2 times, most recently from c03b8e8 to 884aaa1 Compare September 4, 2025 03:39
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch 2 times, most recently from 9c6887b to d06bb4f Compare October 15, 2025 22:35
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch 5 times, most recently from af5b52e to 412b24b Compare October 29, 2025 07:15
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch from 412b24b to 0152638 Compare October 29, 2025 13:01
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch 2 times, most recently from 52c5440 to a64cd00 Compare November 6, 2025 05:13
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch from a64cd00 to 1909630 Compare November 12, 2025 22:45
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch 2 times, most recently from 7f00ec5 to 011da84 Compare December 8, 2025 19:31
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch 3 times, most recently from 8edc08c to d3336ca Compare December 14, 2025 06:04
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch from d3336ca to bb0e768 Compare December 18, 2025 01:02
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch 2 times, most recently from 2fbf5c0 to 22130fb Compare December 30, 2025 00:47
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch 2 times, most recently from 1691a4f to 65c55e9 Compare January 12, 2026 22:24
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch 2 times, most recently from e597f52 to b698c6f Compare January 19, 2026 19:25
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch 2 times, most recently from bf3fac4 to 3083858 Compare January 30, 2026 05:27
@renovate
renovate Bot force-pushed the renovate/golang-dependencies branch 2 times, most recently from 3597a47 to 7498f3e Compare February 10, 2026 09:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies minor-version-golang-dep patch-version-golang-dep

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants