search

fdo-rs / fdo-operator

An OpenShift operator for managing FIDO Device Onboard (FDO) servers
Apache License 2.0
4 stars 2 forks source link

Bump github.com/onsi/ginkgo/v2 from 2.14.0 to 2.15.0 #133

Closed dependabot[bot] closed 10 months ago

dependabot[bot] commented 10 months ago

Bumps github.com/onsi/ginkgo/v2 from 2.14.0 to 2.15.0.

Release notes

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

v2.15.0

2.15.0

Features

  • JUnit reports now interpret Label(owner:X) and set owner to X. [8f3bd70]
  • include cancellation reason when cancelling spec context [96e915c]

Fixes

  • emit output of failed go tool cover invocation so users can try to debug things for themselves [c245d09]
  • fix outline when using nodot in ginkgo v2 [dca77c8]
  • Document areas where GinkgoT() behaves differently from testing.T [dbaf18f]
  • bugfix(docs): use Unsetenv instead of Clearenv (#1337) [6f67a14]

Maintenance

  • Bump to go 1.20 [4fcd0b3]
Changelog

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

2.15.0

Features

  • JUnit reports now interpret Label(owner:X) and set owner to X. [8f3bd70]
  • include cancellation reason when cancelling spec context [96e915c]

Fixes

  • emit output of failed go tool cover invocation so users can try to debug things for themselves [c245d09]
  • fix outline when using nodot in ginkgo v2 [dca77c8]
  • Document areas where GinkgoT() behaves differently from testing.T [dbaf18f]
  • bugfix(docs): use Unsetenv instead of Clearenv (#1337) [6f67a14]

Maintenance

  • Bump to go 1.20 [4fcd0b3]
Commits
  • 7fa0190 v2.15.0
  • c245d09 emit output of failed go tool cover invocation so users can try to debug thin...
  • dca77c8 fix outline when using nodot inginkgo v2
  • 96e915c include cancellation reason when cancelling spec context
  • 4fcd0b3 Bump to go 1.20
  • 732abbc clarify that last owner label wins
  • 8f3bd70 JUnit reports now interpret Label(owner:X) and set owner to X.
  • dbaf18f Document areas where GinkgoT() behaves differently from testing.T
  • 6f67a14 bugfix(docs): use Unsetenv instead of Clearenv (#1337)
  • See full diff in compare view


Dependabot compatibility score

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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
empovit commented 10 months ago

@dependabot rebase