Update all non-major dependencies #229
Open
+13
−7
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:
2.23.4→2.27.4v1.19.1→v1.19.21.24.1→1.25.51.24.1→1.25.5v0.38.0→v0.39.01.64.6→1.64.8Release Notes
onsi/ginkgo (ginkgo)
v2.27.4Compare Source
Fixes
59bc751]v2.27.3Compare Source
Fixes
report exit result in case of failure [
1c9f356]fix data race [
ece19c8]v2.27.2Compare Source
Fixes
a69113a]Maintenance
a99c6e0]f993df5]v2.27.1Compare Source
Fixes
606c1cb]a6463b3]v2.27.0Compare Source
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
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
Fixes
f01aed1]v2.25.2Compare Source
Fixes
Add github output group for progress report content
Maintenance
Bump Gomega
v2.25.1Compare Source
Fixes
10866d3]2e42cff]v2.25.0Compare Source
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
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
goccy/go-yaml (github.com/goccy/go-yaml)
v1.19.2: 1.19.2Compare Source
What's Changed
New Contributors
Full Changelog: goccy/go-yaml@v1.19.1...v1.19.2
golang/go (go)
v1.25.5v1.25.4v1.25.3v1.25.2v1.25.1v1.25.0v1.24.11v1.24.10v1.24.9v1.24.8v1.24.7v1.24.6v1.24.5v1.24.4v1.24.3v1.24.2golangci/golangci-lint (golangci-lint)
v1.64.8Compare Source
golangci-lintis a free and open-source project built by volunteers.If you value it, consider supporting us, the maintainers and linter authors.
We appreciate it! ❤️
For key updates, see the changelog.
Changelog
8b37f14fix: check version of the configuration (#5564)v1.64.7Compare Source
golangci-lintis a free and open-source project built by volunteers.If you value it, consider supporting us, the maintainers and linter authors.
We appreciate it! ❤️
For key updates, see the changelog.
Changelog
94946f3build(deps): bump github.com/OpenPeeDeeP/depguard/v2 from 2.2.0 to 2.2.1 (#5509)132365ebuild(deps): bump github.com/golangci/dupl from3e9179atof665c8d(#5512)bddd1bcbuild(deps): bump github.com/securego/gosec/v2 from 2.22.1 to 2.22.2 (#5515)624fb4ebuild(deps): bump golang.org/x/mod from 0.23.0 to 0.24.0 (#5507)8cffdb7build(deps): bump golang.org/x/oauth2 from 0.27.0 to 0.28.0 in /scripts/gen_github_action_config in the scripts group (#5521)7a3f3d7build(deps): bump golang.org/x/tools from 0.30.0 to 0.31.0 (#5508)c13fd5bbuild(deps): bump honnef.co/go/tools from 0.6.0 to 0.6.1 (#5510)Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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.
This PR was generated by Mend Renovate. View the repository job log.