-
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.
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
28d5c0c to
65b856d
Compare
0272d87 to
9dae15e
Compare
aea74a4 to
e824204
Compare
e4ea544 to
2e836b6
Compare
94a7025 to
cb662ab
Compare
8c3ebbe to
afc054e
Compare
9e0920f to
8799a18
Compare
8799a18 to
9351984
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
9351984 to
8ad90da
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.1v1.8.2->v1.13.0v6.3.0->v6.4.0v1.4.2->v1.4.3v2.22.2->v2.27.1v1.36.2->v1.38.2v1.10.0->v1.11.11.24.0-alpine3.20->1.24.3-alpine3.201.24.0-alpine3.20->1.24.3-alpine3.20v0.32.2->v0.34.1v0.32.2->v0.34.1v0.32.2->v0.34.1v1.9.5->v1.11.2v0.20.2->v0.22.3Release Notes
go-logr/logr (github.com/go-logr/logr)
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.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]onsi/gomega (github.com/onsi/gomega)
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]stretchr/testify (github.com/stretchr/testify)
v1.11.1Compare 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.0Compare 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.1Compare Source
v0.34.0Compare Source
v0.33.5Compare Source
v0.33.4Compare Source
v0.33.3Compare Source
v0.33.2Compare Source
v0.33.1Compare Source
v0.33.0Compare Source
v0.32.9Compare Source
v0.32.8Compare Source
v0.32.7Compare Source
v0.32.6Compare Source
v0.32.5Compare Source
v0.32.4Compare Source
v0.32.3Compare Source
kubernetes/apimachinery (k8s.io/apimachinery)
v0.34.1Compare Source
v0.34.0Compare Source
v0.33.5Compare Source
v0.33.4Compare Source
v0.33.3Compare Source
v0.33.2Compare Source
v0.33.1Compare Source
v0.33.0Compare Source
v0.32.9Compare Source
v0.32.8Compare Source
v0.32.7Compare Source
v0.32.6Compare Source
v0.32.5Compare Source
v0.32.4Compare Source
v0.32.3Compare Source
kubernetes/client-go (k8s.io/client-go)
v0.34.1Compare Source
v0.34.0Compare Source
v0.33.5Compare Source
v0.33.4Compare Source
v0.33.3Compare Source
v0.33.2Compare Source
v0.33.1Compare Source
v0.33.0Compare Source
v0.32.9Compare Source
v0.32.8Compare Source
v0.32.7Compare Source
v0.32.6Compare Source
v0.32.5Compare Source
v0.32.4Compare Source
v0.32.3Compare Source
kubernetes-sigs/cluster-api (sigs.k8s.io/cluster-api)
v1.11.2Compare Source
👌 Kubernetes version support
More information about version support can be found here
Changes since v1.11.1
📈 Overview
✨ New Features
🐛 Bug Fixes
🌱 Others
📖 Additionally, there has been 1 contribution to our documentation and book. (#12780)
Dependencies
Added
Nothing has changed.
Changed
Removed
Nothing has changed.
Thanks to all our contributors! 😊
v1.11.1Compare 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.0Compare 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.Conditionstypes and the new condition semantichas been completed.
FailureReasonandFailureMessagefields have been dropped.*int32fields with units being part of the field name.boolfields have been changed to*boolto preserve user intent.requiredandoptionalis explicitly set in the API, and thatboth serialization and validation works accordingly:
omitemptyand 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).0when 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).requiredandoptionalaccording to K8s API guidelines, extensive work has been done todrop unnecessary pointers thus improving the usability of the API's Go structs.
deletionstruct in all resources.rollouthave been logically grouped in all resources.remediationhave been logically grouped in all resources.See [Cluster API v1.10 compared to v1.11](
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.