Bump github.com/onsi/ginkgo/v2 from 2.7.0 to 2.9.0

[dependabot]

Bumps github.com/onsi/ginkgo/v2 from 2.7.0 to 2.9.0.

Release notes

Sourced from github.com/onsi/ginkgo/v2's releases.

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

2.8.4

Features

• Add OmitSuiteSetupNodes to JunitReportConfig (#1147) [979fbc2]
• Add a reference to ginkgolinter in docs.index.md (#1143) [8432589]

Fixes

• rename tools hack to see if it fixes things for downstream users [a8bb39a]

Maintenance

• Bump golang.org/x/text (#1144) [41b2a8a]
• Bump github.com/onsi/gomega from 1.27.0 to 1.27.1 (#1142) [7c4f583]

v2.8.3

2.8.3

Released to fix security issue in golang.org/x/net dependency

Maintenance

• Bump golang.org/x/net from 0.6.0 to 0.7.0 (#1141) [fc1a02e]
• remove tools.go hack from documentation [0718693]

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.

Maintenance

• Bump github.com/onsi/gomega from 1.26.0 to 1.27.0 (#1139) [5767b0a]
• Fix minor typos (#1138) [e1e9723]
• Fix link in V2 Migration Guide (#1137) [a588f60]

v2.8.1

2.8.1

Fixes

• lock around default report output to avoid triggering the race detector when calling By from goroutines [2d5075a]

... (truncated)

Changelog

Sourced from github.com/onsi/ginkgo/v2's changelog.

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.

2.8.4

Features

• Add OmitSuiteSetupNodes to JunitReportConfig (#1147) [979fbc2]
• Add a reference to ginkgolinter in docs.index.md (#1143) [8432589]

Fixes

• rename tools hack to see if it fixes things for downstream users [a8bb39a]

Maintenance

• Bump golang.org/x/text (#1144) [41b2a8a]
• Bump github.com/onsi/gomega from 1.27.0 to 1.27.1 (#1142) [7c4f583]

2.8.3

Released to fix security issue in golang.org/x/net dependency

Maintenance

• Bump golang.org/x/net from 0.6.0 to 0.7.0 (#1141) [fc1a02e]
• remove tools.go hack from documentation [0718693]

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.

Maintenance

• Bump github.com/onsi/gomega from 1.26.0 to 1.27.0 (#1139) [5767b0a]
• Fix minor typos (#1138) [e1e9723]
• Fix link in V2 Migration Guide (#1137) [a588f60]

2.8.1

Fixes

• lock around default report output to avoid triggering the race detector when calling By from goroutines [2d5075a]
• don't run ReportEntries through sprintf [febbe38]

Maintenance

• Bump golang.org/x/tools from 0.5.0 to 0.6.0 (#1135) [11a4860]
• test: update matrix for Go 1.20 (#1130) [4890a62]

... (truncated)

Commits

• 2470852 v2.9.0
• 8cda4ef ignore empty progress reports
• 119f1d8 note that AttachProgressReporter is an experimental feature
• ae8c900 handle failures and panics in attached progress reporters
• b670c81 go mod tidy
• 2bd5a3b Expand GinkgoT() to include several Ginkgo-specific methods
• 28801fe AttachProgressReporter allows users to provide arbitrary information when a P...
• da91bbf v2.8.4
• 979fbc2 Add OmitSuiteSetupNodes to JunitReportConfig (#1147)
• a8bb39a rename tools hack to see if it fixes things for downstream users
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)