snivilised / cobrass

🐲 Assistant for cli applications using cobra
https://pkg.go.dev/github.com/snivilised/cobrass
MIT License
1 stars 0 forks source link

chore(deps): bump github.com/onsi/ginkgo/v2 from 2.14.0 to 2.15.0 #262

Closed dependabot[bot] closed 9 months ago

dependabot[bot] commented 9 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 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)
dependabot[bot] commented 9 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.