fix(deps): update golang-dependencies #22
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
renovate
bot
force-pushed
the
renovate/golang-dependencies
branch
3 times, most recently
from
f5ee957 to
75b42ac
Compare
renovate
bot
force-pushed
the
renovate/golang-dependencies
branch
2 times, most recently
from
56136d8 to
3e03646
Compare
renovate
bot
force-pushed
the
renovate/golang-dependencies
branch
3 times, most recently
from
152277f to
56a1ef7
Compare
renovate
bot
force-pushed
the
renovate/golang-dependencies
branch
3 times, most recently
from
f49ee66 to
71157d7
Compare
renovate
bot
force-pushed
the
renovate/golang-dependencies
branch
6 times, most recently
from
d5ce63f to
89d4cee
Compare
renovate
bot
force-pushed
the
renovate/golang-dependencies
branch
6 times, most recently
from
97dd4ee to
340b5f7
Compare
renovate
bot
force-pushed
the
renovate/golang-dependencies
branch
from
340b5f7 to
fa0f5a6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.4.1->v1.4.3v2.17.1->v2.25.1v1.32.0->v1.38.2v1.8.4->v1.11.1v1.6.1->v1.11.1v2.3.0->v2.4.0v0.30.1->v0.34.0v0.30.1->v0.34.0v0.30.1->v0.34.0v0.18.4->v0.22.0Warning
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.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
onsi/ginkgo (github.com/onsi/ginkgo/v2)
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]4ce33f4]f2fcd97]fd622d2]5474a26]e6d1170]7f447b2]f15239a]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]v1.36.2Compare Source
Maintenance
v1.36.1Compare Source
1.36.1
Fixes
1c6c112]4feb9d7]v1.36.0Compare Source
1.36.0
Features
4c964c6]Maintenance
ece6872]8e924d7]v1.35.1Compare Source
1.35.1
Fixes
ca36da1]v1.35.0Compare Source
1.35.0
Features
EnforceDefaultTimeoutsWhenUsingContexts()to haveEventuallyhonor the default timeout when passed a context. (prior to this you had to expclility add a timeout) [e4c4265]StopTrying(message).Successfully()to abort aConsistentlyearly without failure [eeca931]Fixes
HaveFieldto avoid unexpected errors when used with async assertions. [3bdbc4e]Maintenance
a05a416]v1.34.2Compare Source
1.34.2
Require Go 1.22+
Maintenance
c59c6dc]8158b99]v1.34.1Compare Source
1.34.1
Maintenance
5e71dcd]v1.34.0Compare Source
1.34.0
Features
c549e0d]Fixes
878940c]ebadb67]Maintenance
8af2ece]123a071]0e69083]2675796]4160c0f]892c303]v1.33.1Compare Source
1.33.1
Fixes
3a66379]Maintenance
e9bc35a]v1.33.0Compare Source
1.33.0
Features
Receivenot acceptsReceive(<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
9999deb]cb5ff21]bac6596]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
v1.10.0Compare Source
What's Changed
Functional Changes
Fixes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.