deps(deps): update all non-major dependencies#381
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
7653d9b to
740ac02
Compare
740ac02 to
0b04acf
Compare
0b04acf to
bd6dcf4
Compare
bd6dcf4 to
12b1a6b
Compare
12b1a6b to
1cd8cd7
Compare
1cd8cd7 to
48ae030
Compare
48ae030 to
7f96ff3
Compare
9736c59 to
72cb251
Compare
fac8007 to
2947ddd
Compare
2947ddd to
dbeef25
Compare
1c25115 to
68d28ca
Compare
68d28ca to
d62431a
Compare
539dfaf to
b2761ce
Compare
347cd4a to
1b5ff66
Compare
06dd8dd to
be6bce8
Compare
a9beb66 to
029d318
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
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
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:
v0.9.1→v0.12.0v1.4.2→v1.4.3v0.20.3→v0.21.6v2.22.2→v2.29.0v1.36.2→v1.41.0v2.4.3→v2.6.3v1.8.15→v1.10.6v1.10.0→v1.11.1v0.32.2→v0.36.1v0.32.2→v0.36.1v0.32.2→v0.36.1v2.130.1→v2.140.0v1.9.5→v1.13.2v0.20.2→v0.24.1Release Notes
awslabs/amazon-ecr-credential-helper (github.com/awslabs/amazon-ecr-credential-helper/ecr-login)
v0.12.0: Amazon ECR Credential Helper - Release v0.12.0Compare Source
Assets
v0.11.0: Amazon ECR Credential Helper - Release v0.11.0Compare Source
Assets
v0.10.1: Amazon ECR Credential Helper - Release v0.10.1Compare Source
Assets
v0.10.0: Amazon ECR Credential Helper - Release v0.10.0Compare Source
Assets
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
google/go-containerregistry (github.com/google/go-containerregistry)
v0.21.6Compare Source
What's Changed
New Contributors
Full Changelog: google/go-containerregistry@v0.21.5...v0.21.6
v0.21.5Compare Source
What's Changed
Full Changelog: google/go-containerregistry@v0.21.4...v0.21.5
v0.21.4Compare Source
What's Changed
New Contributors
Full Changelog: google/go-containerregistry@v0.21.3...v0.21.4
v0.21.3Compare Source
What's Changed
crane indexsubcommand by @edwardthiele in #2223New Contributors
Full Changelog: google/go-containerregistry@v0.21.2...v0.21.3
v0.21.2Compare Source
What's Changed
Full Changelog: google/go-containerregistry@v0.21.1...v0.21.2
v0.21.1Compare Source
This release fixes a regression in
craneintroduced in the previous release.What's Changed
New Contributors
Full Changelog: google/go-containerregistry@v0.21.0...v0.21.1
v0.21.0Compare Source
This release updates the minimum Go version to
1.25.6.What's Changed
New Contributors
Full Changelog: google/go-containerregistry@v0.20.7...v0.21.0
v0.20.8Compare Source
v0.20.7Compare Source
What's Changed
New Contributors
Full Changelog: google/go-containerregistry@v0.20.6...v0.20.7
v0.20.6Compare Source
What's Changed
New Contributors
Full Changelog: google/go-containerregistry@v0.20.4...v0.20.6
v0.20.5Compare Source
What's Changed
New Contributors
Full Changelog: google/go-containerregistry@v0.20.3...v0.20.5
v0.20.4: - Not usable as a go moduleCompare Source
🚨 This release was published to the Go module proxy and then re-tagged with a different commit. This means it's not usable as a Go module (#2107) -- please us v0.20.5 instead.
What's Changed
New Contributors
Full Changelog: google/go-containerregistry@v0.20.3...v0.20.4
onsi/ginkgo (github.com/onsi/ginkgo/v2)
v2.29.0Compare Source
2.29.0
GinkgoHelperGomakes it easier to write test helpers that need to run in goroutines. Specifically, it makes managing the failure state and capturing failure panics correctly straightforward.ginkgo outlinenow includes entries defined inDescribeTableSubtreev2.28.3Compare Source
2.28.3
Maintenance
Bump all dependencies
v2.28.2Compare Source
2.28.2
f3a36b6]94151c8]4d21dbb]c102161]9619647]5779304]v2.28.1Compare Source
2.28.1
Update all dependencies. This auto-updated the required version of Go to 1.24, consistent with the fact that Go 1.23 has been out of support for almost six months.
v2.28.0Compare Source
2.28.0
Ginkgo's SemVer filter now supports filtering multiple components by SemVer version:
can be filtered in or out with an invocation like:
ginkgo --sem-ver-filter="2.1.1, redis=8.2.0"Huge thanks to @Icarus9913 for working on this!
v2.27.5Compare Source
2.27.5
Fixes
Don't make a new formatter for each GinkgoT(); that's just silly and uses precious memory
v2.27.4Compare Source
2.27.4
Fixes
59bc751]v2.27.3Compare Source
2.27.3
Fixes
report exit result in case of failure [
1c9f356]fix data race [
ece19c8]v2.27.2Compare Source
2.27.2
Fixes
a69113a]Maintenance
a99c6e0]f993df5]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.3](https://redirect.github.com/onsi/ginkgo/releases/tag/v2.Configuration
📅 Schedule: (UTC)
🚦 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.