Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 5, 2025

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.2 -> v1.4.3 age confidence
github.com/onsi/ginkgo/v2 v2.22.2 -> v2.27.3 age confidence
github.com/onsi/gomega v1.36.2 -> v1.38.3 age confidence
github.com/stretchr/testify v1.10.0 -> v1.11.1 age confidence
k8s.io/api v0.32.2 -> v0.34.3 age confidence
k8s.io/apimachinery v0.32.2 -> v0.34.3 age confidence
k8s.io/client-go v0.32.2 -> v0.34.3 age confidence
sigs.k8s.io/cluster-api v1.9.5 -> v1.12.0 age confidence
sigs.k8s.io/controller-runtime v0.20.2 -> v0.22.4 age confidence

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

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

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
  • Bump rexml from 3.4.0 to 3.4.2 in /docs (#​1595) [1333dae]
  • Bump github.com/gkampitakis/go-snaps from 0.5.14 to 0.5.15 (#​1600) [17ae63e]

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
onsi/gomega (github.com/onsi/gomega)

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

New Contributors

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

kubernetes/api (k8s.io/api)

v0.34.3

Compare Source

v0.34.2

Compare Source

v0.34.1

Compare Source

v0.34.0

Compare Source

v0.33.7

Compare Source

v0.33.6

Compare Source

v0.33.5

Compare Source

v0.33.4

Compare Source

v0.33.3

Compare Source

v0.33.2

Compare Source

v0.33.1

Compare Source

v0.33.0

Compare Source

v0.32.10

Compare Source

v0.32.9

Compare Source

v0.32.8

Compare Source

v0.32.7

Compare Source

v0.32.6

Compare Source

v0.32.5

Compare Source

v0.32.4

Compare Source

v0.32.3

Compare Source

kubernetes/apimachinery (k8s.io/apimachinery)

v0.34.3

Compare Source

v0.34.2

Compare Source

v0.34.1

Compare Source

v0.34.0

Compare Source

v0.33.7

Compare Source

v0.33.6

Compare Source

v0.33.5

Compare Source

v0.33.4

Compare Source

v0.33.3

Compare Source

v0.33.2

Compare Source

v0.33.1

Compare Source

v0.33.0

Compare Source

v0.32.10

Compare Source

v0.32.9

Compare Source

v0.32.8

Compare Source

v0.32.7

Compare Source

v0.32.6

Compare Source

v0.32.5

Compare Source

v0.32.4

Compare Source

v0.32.3

Compare Source

kubernetes/client-go (k8s.io/client-go)

v0.34.3

Compare Source

v0.34.2

Compare Source

v0.34.1

Compare Source

v0.34.0

Compare Source

v0.33.7

Compare Source

v0.33.6

Compare Source

v0.33.5

Compare Source

v0.33.4

Compare Source

v0.33.3

Compare Source

v0.33.2

Compare Source

v0.33.1

Compare Source

v0.33.0

Compare Source

v0.32.10

Compare Source

v0.32.9

Compare Source

v0.32.8

Compare Source

v0.32.7

Compare Source

v0.32.6

Compare Source

v0.32.5

Compare Source

v0.32.4

Compare Source

v0.32.3

Compare Source

kubernetes-sigs/cluster-api (sigs.k8s.io/cluster-api)

v1.12.0

Compare Source

👌 Kubernetes version support

  • Management Cluster: v1.31.x -> v1.34.x
  • Workload Cluster: v1.29.x -> v1.34.x

More information about version support can be found here

Highlights

  • Bumped to Go 1.24, controller-runtime v0.22, k8s.io/* v0.34, controller-gen v0.19
  • In-place updates
    • Cluster API introduces support for update extensions allowing users to execute changes on existing machines without deleting the machines and creating a new one.
    • Both KCP and Machine deployments support in-place updates based on the new update extension
    • Can be enabled with the new InPlaceUpdates feature gate
    • More details can be found in the proposal
  • Chained upgrades
    • Clusters using managed topologies can now upgrade by more than one minor Kubernetes version by performing chained and efficient upgrades.
    • Upgrade plan will be computed using Kubernetes version from the ClusterClass or by calling a new runtimeExtension (also defined in the ClusterClass)
    • Existing lifecycle hooks have been adapted to the new workflow, new lifecycle hooks have been introduced to allow granular control of the upgrade steps.
    • More details can be found in the proposal
  • MachineHealthCheck: Add support for checking Machine conditions (#​12827)
  • Machine: First part of the Taint propagation proposal (Machine/MachineSet/MachineDeployment) (#​12936, #​12966)
  • KCP/CABPK: Add EncryptionAlgorithm field to Kubeadmconfig to support keys generated with RSA-3072, RSA-4096, ECDSA-P256, ECDSA-P384 (#​12859)
  • Introduce ReconcilerRateLimiting feature (#​13006)
    • Can be enabled with the new ReconcilerRateLimiting feature gate
    • Rate-limits all reconcilers to at most 1 request per second

Note: Cluster API is only supported on conformant Kubernetes Clusters and contract-relevant provider resources (e.g. InfraCluster) have to be implemented as CRDs (i.e. not via an aggregated apiserver).

Other changes

  • clusterctl: Add conditions filter for clusterctl describe (#​12991)
  • clusterctl: clusterctl move blocks when Cluster or ClusterClass is paused (#​12786)
  • KCP: Enable websocket dialer with fallback to spdy (for communication with etcd) (#​12902)
  • Runtime SDK: Add defensive response status checking in runtime client (#​12898)
  • Improved logging across several controllers
  • Improved e2e test coverage, e.g.: CAPD: Add scale from/to 0 support for CAPD (#​12572)
  • New providers in clusterctl: HCP (#​12800) control plane provider, Metal3 IPAM provider (#​12756), metal-stack infrastructure provider (#​12925)

Deprecation and Removals Warning

For additional details for providers, please take a look at Cluster API v1.11 compared to v1.12.

Changes since v1.11.0

📈 Overview

  • 298 new commits merged
  • 5 breaking changes ⚠️
  • 42 feature additions ✨
  • 42 bugs fixed 🐛

⚠️ Breaking Changes

  • CI: Improve KAL config docs for forbidding OpenAPI defaulting (#​12869)
  • clusterctl: Block move when Cluster or ClusterClass is paused (#​12786)
  • Dependency: Bump to controller-runtime v0.22 & controller-tools v0.19 (#​12634)
  • Runtime SDK: Improve chained upgrade observability (#​12973)
  • Runtime SDK: Make the AfterClusterUpgrade hook blocking (#​12984)

✨ New Features

  • API/Machine/MachineSet/MachineDeployment: Machine related API changes, conversion and feature gate (#​12936)
  • CABPK: Add EncryptionAlgorithm to Kubeadmconfig (#​12859)
  • CAPD: Add scale from/to 0 support for CAPD (#​12572)
  • CI: Bump autoscaler to a9cb59f (#​12643)
  • CI: Bump Kubernetes in tests to v1.34.0 and claim support for v1.34 (#​12699)
  • ClusterCache/KCP: Deprecate GetClientCertificatePrivateKey and stop using it in KCP (#​12846)
  • ClusterCache: Add GetUncachedClient() (#​12803)
  • ClusterClass: Add .spec.upgrade.external.generateUpgradePlanExtension field to ClusterClass (#​12809)
  • ClusterClass: Add types and hook for GenerateUpgradePlan (#​12823)
  • ClusterClass: Additional validation in Cluster/ClusterClass webhook for chained upgrades (#​12816)
  • ClusterClass: Call GenerateUpgradePlanRequest Runtime Extension (#​12903)
  • ClusterClass: Implement core logic for chained upgrades (#​12726)
  • clusterctl: Add conditions filter for clusterctl describe (#​12991)
  • Control-plane: Add new control-plane provider HCP (#​12800)
  • e2e: Bump Kubernetes version used for testing to v1.34.0-rc.1 (#​12623)
  • e2e: Bump Kubernetes version used for testing to v1.34.0-rc.2 (#​12658)
  • e2e: Bump Kubernetes version used for testing to v1.35.0-beta.0 (#​13029)
  • e2e: Change RuntimeSDK e2e test ClusterClass to use GenerateUpgradePlan extension (#​12955)
  • e2e: Implement e2e test for in-place updates (#​12938)
  • KCP/CABPK/CI: Bump KAL to pick up latest requiredfields linter, add Min/MaxLength to BootstrapToken (#​12563)
  • KCP/MachineSet: Refactor BootstrapConfig/InfraMachine managedFields for in-place (#​12890)
  • KCP: Bump coredns/corefile-migration to v1.0.28 (#​12748)
  • KCP: Bump coredns/corefile-migration to v1.0.29 (#​12862)
  • KCP: Bump corefile-migration to v1.0.27 (#​12636)
  • KCP: Compare ClusterConfiguration via KubeadmConfig instead of annotation on Machine (#​12758)
  • KCP: Extend rollout logic for in-place updates (#​12840)
  • KCP: Implement CanUpdateMachine (#​12857)
  • KCP: Implement trigger in-place update (#​12897)
  • Machine: Add in-place updates support for machine controller (#​12831)
  • MachineDeployment: Add in-place to rollout planner (#​12865)
  • MachineDeployment: Implement CanUpdateMachineSet (#​12965)
  • MachineHealthCheck: Add support for checking Machine conditions in MachineHealthCheck (#​12827)
  • Misc: Add inplace updates featuregate ([#​12755](https://redirect.github.com/kubernete

Configuration

📅 Schedule: 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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner March 5, 2025 23:18
@renovate renovate bot requested a review from arturshadnik March 5, 2025 23:18
@renovate
Copy link
Contributor Author

renovate bot commented Mar 5, 2025

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 27 additional dependencies were updated

Details:

Package Change
github.com/emicklei/go-restful/v3 v3.12.1 -> v3.12.2
github.com/fsnotify/fsnotify v1.7.0 -> v1.8.0
github.com/google/go-cmp v0.6.0 -> v0.7.0
github.com/google/pprof v0.0.0-20241210010833-40e02aabc2ad -> v0.0.0-20250403155104-27863c87afa6
github.com/spf13/cobra v1.8.1 -> v1.9.1
github.com/spf13/pflag v1.0.5 -> v1.0.6
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.53.0 -> v0.54.0
go.opentelemetry.io/otel v1.28.0 -> v1.29.0
go.opentelemetry.io/otel/metric v1.28.0 -> v1.29.0
go.opentelemetry.io/otel/sdk v1.28.0 -> v1.29.0
go.opentelemetry.io/otel/trace v1.28.0 -> v1.29.0
golang.org/x/net v0.33.0 -> v0.37.0
golang.org/x/oauth2 v0.24.0 -> v0.28.0
golang.org/x/sync v0.10.0 -> v0.12.0
golang.org/x/sys v0.28.0 -> v0.32.0
golang.org/x/term v0.27.0 -> v0.30.0
golang.org/x/text v0.21.0 -> v0.23.0
golang.org/x/time v0.7.0 -> v0.8.0
golang.org/x/tools v0.28.0 -> v0.31.0
gomodules.xyz/jsonpatch/v2 v2.4.0 -> v2.5.0
google.golang.org/genproto/googleapis/api v0.0.0-20240826202546-f6391c0de4c7 -> v0.0.0-20241209162323-e6fa225c2576
google.golang.org/genproto/googleapis/rpc v0.0.0-20240826202546-f6391c0de4c7 -> v0.0.0-20241223144023-3abc09e42ca8
google.golang.org/grpc v1.65.1 -> v1.67.3
google.golang.org/protobuf v1.36.1 -> v1.36.5
k8s.io/apiextensions-apiserver v0.32.1 -> v0.32.3
k8s.io/apiserver v0.32.1 -> v0.32.3
k8s.io/component-base v0.32.1 -> v0.32.3

renovate-approve[bot]
renovate-approve bot previously approved these changes Mar 5, 2025
@dosubot dosubot bot added the size:S This PR changes 10-29 lines, ignoring generated files. label Mar 5, 2025
@renovate renovate bot changed the title deps(deps): update module github.com/onsi/ginkgo/v2 to v2.23.0 deps(deps): update all non-major dependencies Mar 8, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0ab1664 to c86a774 Compare March 8, 2025 13:48
renovate-approve[bot]
renovate-approve bot previously approved these changes Mar 8, 2025
renovate-approve[bot]
renovate-approve bot previously approved these changes Mar 12, 2025
renovate-approve[bot]
renovate-approve bot previously approved these changes Mar 18, 2025
renovate-approve[bot]
renovate-approve bot previously approved these changes Mar 19, 2025
renovate-approve[bot]
renovate-approve bot previously approved these changes Mar 20, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e4e1c55 to d4ac801 Compare March 21, 2025 23:00
@dosubot dosubot bot added size:M This PR changes 30-99 lines, ignoring generated files. and removed size:S This PR changes 10-29 lines, ignoring generated files. labels Mar 21, 2025
renovate-approve[bot]
renovate-approve bot previously approved these changes Mar 21, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 2542a30 to 4cd90d9 Compare August 31, 2025 10:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from df37008 to e827ec1 Compare September 10, 2025 09:44
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 80e315f to 3ada6f5 Compare October 2, 2025 14:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 7186b44 to 71421d4 Compare October 11, 2025 01:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 1ce9ba5 to 607432f Compare October 27, 2025 22:07
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 71c2129 to a2d4120 Compare November 4, 2025 20:34
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 9ac8714 to 5de3353 Compare November 14, 2025 18:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 107fa9d to 431dd0a Compare November 20, 2025 08:31
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 45e2d82 to ddab3b3 Compare December 9, 2025 19:13
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from ddab3b3 to 36b3a8f Compare December 10, 2025 05:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies go size:S This PR changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant