-
Notifications
You must be signed in to change notification settings - Fork 0
deps(deps): update all non-major dependencies #370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/all-minor-patch
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+14
−14
Conversation
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
26348af
to
4e53bc1
Compare
4e53bc1
to
4168fe8
Compare
4168fe8
to
a41cf37
Compare
a41cf37
to
2626fb1
Compare
2626fb1
to
a44d868
Compare
a44d868
to
70eff56
Compare
70eff56
to
961944f
Compare
776a3a6
to
d7e6a2e
Compare
a7d162f
to
fe35d38
Compare
5e2d2c5
to
f71774d
Compare
f71774d
to
c89119a
Compare
5c00886
to
c03850b
Compare
3e1980f
to
9f218bc
Compare
e4f5f73
to
6576a68
Compare
68583cf
to
aea74a4
Compare
aea74a4
to
e824204
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
e824204
to
85df849
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
0 participants
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.17.0
->v1.19.0
v1.8.2
->v1.11.0
v6.3.0
->v6.4.0
v1.4.2
->v1.4.3
v2.22.2
->v2.25.3
v1.36.2
->v1.38.2
v1.10.0
->v1.11.1
1.24.0-alpine3.20
->1.24.3-alpine3.20
1.24.0-alpine3.20
->1.24.3-alpine3.20
v0.32.2
->v0.34.0
v0.32.2
->v0.34.0
v0.32.2
->v0.34.0
v1.9.5
->v1.11.1
v0.20.2
->v0.22.0
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.25.3
Compare Source
2.25.3
Fixes
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
10866d3
]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 andbody
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
andDeferCleanup
,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 callruntime.LockOSThread()
in theAroundNode
to ensure that the node runs on a single thread).Since
AroundNode
allows you to modify the context you can also useAroundNode
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 likeBeforeEach
andDeferCleanup
.AroundNode
can also be applied toRunSpecs
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")
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.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
2b9c428
]Fixes
1f59d07
]Maintenance
2d134d5
]v2.23.3
Compare Source
2.23.3
Fixes
-
as a standalone argument [cfcc1a5
]feaf292
]88e2282
]v2.23.2
Compare Source
2.23.2
🎉🎉🎉
At long last, some long-standing performance gaps between
ginkgo
andgo 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 ofgo test -c
is slower thango test
's compilation step becausego test
strips out debug symbols (ldflags=-w
) whereasgo test -c
does not.Ginkgo now passes the appropriate
ldflags
togo 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 whenginkgo 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:
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.0
Compare Source
2.23.0
Ginkgo 2.23.0 adds a handful of methods to
GinkgoT()
to make it compatible with thetesting.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 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
]onsi/gomega (github.com/onsi/gomega)
v1.38.2
Compare Source
1.38.2
c404969
]v1.38.1
Compare Source
1.38.1
Fixes
Numerous minor fixes and dependency bumps
v1.38.0
Compare Source
1.38.0
Features
4ee7ed0
]Fixes
36bbf72
]Maintenance
529d408
]acd1f55
]bae65a0
]8dda91f
]212d812
]59bd7f9
]328c729
]9a798a1
]04a72c6
]v1.37.0
Compare Source
1.37.0
Features
5666f98
]v1.36.3
Compare Source
1.36.3
Maintenance
adb8b49
]interface{}
withany
[7613216
]9fe5259
]a0e85b9
]604a8b1
]36fbc84
]ced70d7
]c8b4a07
]06431b9
]b55a92d
]a1d518b
]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.0
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.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.0
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.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.0
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.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.11.1
Compare Source
👌 Kubernetes version support
More information about version support can be found here
Changes since v1.11.0
📈 Overview
✨ New Features
a9cb59f
(#12707)🐛 Bug Fixes
🌱 Others
📖 Additionally, there have been 4 contributions to our documentation and book. (#12667, #12668, #12671, #12674)
Dependencies
Added
Nothing has changed.
Changed
Removed
Nothing has changed.
Thanks to all our contributors! 😊
v1.11.0
Compare Source
👌 Kubernetes version support
More information about version support can be found here
Highlights
sigs.k8s.io/randfill
) (#12191)step in the journey towards graduating our API to v1.
metav1.Conditions
types and the new condition semantichas been completed.
FailureReason
andFailureMessage
fields have been dropped.*int32
fields with units being part of the field name.bool
fields have been changed to*bool
to preserve user intent.required
andoptional
is explicitly set in the API, and thatboth serialization and validation works accordingly:
omitempty
and introduction ofomitzero
)""
when it is not semantically different from value not set (either you have to provide a non-empty string value or not set the field at all).0
when it is not semantically different from value not set (either you have to provide a non-0 int value or not set the field at all).{}
when it is not semantically different from value not set (either you have to set at least one property in the object or not set the field at all).[]
when it is not semantically different from value not set (either you have to set at least one item in the list or not set the field at all).required
andoptional
according to K8s API guidelines, extensive work has been done todrop unnecessary pointers thus improving the usability of the API's Go structs.
deletion
struct in all resources.rollout
have been logically grouped in all resources.remediation
have been logically grouped in all resources.See Cluster API v1.10 compared to v1.11 for more details
Notes for workload cluster upgrade to Kubernetes v1.34 with KCP
Deprecation and Removals Warning
clusterctl alpha topology plan
command (#12283)Changes since v1.10.0
📈 Overview
📝 Proposals
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.
This PR was generated by Mend Renovate. View the repository job log.