-
Notifications
You must be signed in to change notification settings - Fork 0
🌱 Update Update Golang Dependencies group (minor) #228
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
base: main
Are you sure you want to change the base?
Conversation
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
99b9de5 to
819909f
Compare
819909f to
b806939
Compare
c784ddb to
68ea2bc
Compare
d2984ae to
002d33d
Compare
81529d0 to
896645d
Compare
896645d to
ec4c959
Compare
ec4c959 to
d02eb5b
Compare
d02eb5b to
df27822
Compare
d272a0a to
860fabc
Compare
860fabc to
8e55d8d
Compare
50a1135 to
3a2c775
Compare
1022f8f to
e3b1956
Compare
f4bb43f to
c733cf1
Compare
9726f3a to
7c781a5
Compare
833be9e to
38df19c
Compare
38df19c to
b39b545
Compare
|
c451e76 to
a2586ef
Compare
a2586ef to
30d6c2d
Compare
| datasource | package | from | to | | -------------- | ------------------------------------------ | ------- | ------- | | go | github.com/gophercloud/gophercloud/v2 | v2.4.0 | v2.8.0 | | go | github.com/onsi/ginkgo/v2 | v2.22.2 | v2.27.1 | | go | github.com/onsi/gomega | v1.36.2 | v1.38.2 | | go | github.com/stretchr/testify | v1.10.0 | v1.11.1 | | golang-version | go | 1.23.5 | 1.25.3 | | go | sigs.k8s.io/cluster-api-provider-openstack | v0.11.4 | v0.13.0 | | go | sigs.k8s.io/yaml | v1.4.0 | v1.6.0 |
30d6c2d to
0381b8e
Compare
This PR contains the following updates:
v2.4.0->v2.8.0v2.22.2->v2.27.1v1.36.2->v1.38.2v1.10.0->v1.11.11.23.5->1.25.3v0.11.4->v0.13.0v1.4.0->v1.6.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
gophercloud/gophercloud (github.com/gophercloud/gophercloud/v2)
v2.8.0Compare Source
What's Changed
Full Changelog: gophercloud/gophercloud@v2.7.0...v2.8.0
v2.7.0Compare Source
What's Changed
network standard-attr-*extensions by @mandre in https://github.com/gophercloud/gophercloud/pull/3328Full Changelog: gophercloud/gophercloud@v2.6.0...v2.7.0
v2.6.0Compare Source
What's Changed
Full Changelog: gophercloud/gophercloud@v2.5.0...v2.6.0
v2.5.0Compare Source
What's Changed
Full Changelog: gophercloud/gophercloud@v2.4.0...v2.5.0
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-sigs/cluster-api-provider-openstack (sigs.k8s.io/cluster-api-provider-openstack)
v0.13.0Compare Source
Highlights
Changes since v0.12.0
📈 Overview
📝 Proposals
✨ New Features
🐛 Bug Fixes
🌱 Others
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.