Releases: onsi/ginkgo
v2.9.6
v2.9.5
2.9.5
Fixes
- ensure the correct deterministic sort order is produced when ordered specs are generated by a helper function [7fa0b6b]
Maintenance
v2.9.4
2.9.4
Fixes
-
fix hang with ginkgo -p (#1192) [15d4bdc] - this addresses a long standing issue related to Ginkgo hanging when a child process spawned by the test does not exit.
-
fix: fail fast may cause Serial spec or cleanup Node interrupted (#1178) [8dea88b] - prior to this there was a small gap in which specs on other processes might start even if one process has tried to abort the suite.
Maintenance
- Document run order when multiple setup nodes are at the same nesting level [903be81]
v2.9.3
2.9.3
Features
- Add RenderTimeline to GinkgoT() [c0c77b6]
Fixes
- update Measure deprecation message. fixes #1176 [227c662]
- add newlines to GinkgoLogr (#1170) (#1171) [0de0e7c]
Maintenance
- Bump commonmarker from 0.23.8 to 0.23.9 in /docs (#1183) [8b925ab]
- Bump nokogiri from 1.14.1 to 1.14.3 in /docs (#1184) [e3795a4]
- Bump golang.org/x/tools from 0.7.0 to 0.8.0 (#1182) [b453793]
- Bump actions/setup-go from 3 to 4 (#1164) [73ed75b]
- Bump github.com/onsi/gomega from 1.27.4 to 1.27.6 (#1173) [0a2bc64]
- Bump github.com/go-logr/logr from 1.2.3 to 1.2.4 (#1174) [f41c557]
- Bump golang.org/x/sys from 0.6.0 to 0.7.0 (#1179) [8e423e5]
v2.9.2
v2.9.1
v2.9.0
2.9.0
Features
-
AttachProgressReporter is an experimental feature that allows users to provide arbitrary information when a ProgressReport is requested [28801fe]
-
GinkgoT() has been expanded to include several Ginkgo-specific methods [2bd5a3b]
The intent is to enable the development of third-party libraries that integrate deeply with Ginkgo using
GinkgoT()
to access Ginkgo's functionality.
v2.8.4
v2.8.3
v2.8.2
2.8.2
Ginkgo now includes a tools.go
file in the root directory of the ginkgo
package. This should allow modules that simply go get github.com/onsi/ginkgo/v2
to also pull in the CLI dependencies. This obviates the need for consumers of Ginkgo to have their own tools.go
file and makes it simpler to ensure that the version of the ginkgo
CLI being used matches the version of the library. You can simply run go run github.com/onsi/ginkgo/v2/ginkgo
to run the version of the cli associated with your package go.mod.