Bump github.com/onsi/gomega from 1.12.0 to 1.23.0

[dependabot]

Bumps github.com/onsi/gomega from 1.12.0 to 1.23.0.

Release notes

Sourced from github.com/onsi/gomega's releases.

v1.23.0

1.23.0

Features

• Custom formatting on a per-type basis can be provided using format.RegisterCustomFormatter() -- see the docs here

• Substantial improvement have been made to StopTrying():

  • Users can now use StopTrying().Wrap(err) to wrap errors and StopTrying().Attach(description, object) to attach arbitrary objects to the StopTrying() error
  • StopTrying() is now always interpreted as a failure. If you are an early adopter of StopTrying() you may need to change your code as the prior version would match against the returned value even if StopTrying() was returned. Going forward the StopTrying() api should remain stable.
  • StopTrying() and StopTrying().Now() can both be used in matchers - not just polled functions.

• TryAgainAfter(duration) is used like StopTrying() but instructs Eventually and Consistently that the poll should be tried again after the specified duration. This allows you to dynamically adjust the polling duration.

• ctx can now be passed-in as the first argument to Eventually and Consistently.

Maintenance

• Bump github.com/onsi/ginkgo/v2 from 2.3.0 to 2.3.1 (#597) [afed901]
• Bump nokogiri from 1.13.8 to 1.13.9 in /docs (#599) [7c691b3]
• Bump github.com/google/go-cmp from 0.5.8 to 0.5.9 (#587) [ff22665]

v1.22.1

1.22.1

Fixes

• When passed a context and no explicit timeout, Eventually will only timeout when the context is cancelled [e5105cf]
• Allow StopTrying() to be wrapped [bf3cba9]

Maintenance

• bump to ginkgo v2.3.0 [c5d5c39]

v1.22.0

1.22.0

Features

Several improvements have been made to Eventually and Consistently in this and the most recent releases:

• Eventually and Consistently can take a context.Context [65c01bc] This enables integration with Ginkgo 2.3.0's interruptible nodes and node timeouts.
• Eventually and Consistently that are passed a SpecContext can provide reports when an interrupt occurs [0d063c9]
• Eventually/Consistently will forward an attached context to functions that ask for one [e2091c5]
• Eventually/Consistently supports passing arguments to functions via WithArguments() [a2dc7c3]
• Eventually and Consistently can now be stopped early with StopTrying(message) and StopTrying(message).Now() [52976bb]

These improvements are all documented in Gomega's docs

v1.21.1

Features

... (truncated)

Changelog

Sourced from github.com/onsi/gomega's changelog.

1.23.0

Features

• Custom formatting on a per-type basis can be provided using format.RegisterCustomFormatter() -- see the docs here

• Substantial improvement have been made to StopTrying():

  • Users can now use StopTrying().Wrap(err) to wrap errors and StopTrying().Attach(description, object) to attach arbitrary objects to the StopTrying() error
  • StopTrying() is now always interpreted as a failure. If you are an early adopter of StopTrying() you may need to change your code as the prior version would match against the returned value even if StopTrying() was returned. Going forward the StopTrying() api should remain stable.
  • StopTrying() and StopTrying().Now() can both be used in matchers - not just polled functions.

• TryAgainAfter(duration) is used like StopTrying() but instructs Eventually and Consistently that the poll should be tried again after the specified duration. This allows you to dynamically adjust the polling duration.

• ctx can now be passed-in as the first argument to Eventually and Consistently.

Maintenance

• Bump github.com/onsi/ginkgo/v2 from 2.3.0 to 2.3.1 (#597) [afed901]
• Bump nokogiri from 1.13.8 to 1.13.9 in /docs (#599) [7c691b3]
• Bump github.com/google/go-cmp from 0.5.8 to 0.5.9 (#587) [ff22665]

1.22.1

Fixes

• When passed a context and no explicit timeout, Eventually will only timeout when the context is cancelled [e5105cf]
• Allow StopTrying() to be wrapped [bf3cba9]

Maintenance

• bump to ginkgo v2.3.0 [c5d5c39]

1.22.0

Features

Several improvements have been made to Eventually and Consistently in this and the most recent releases:

• Eventually and Consistently can take a context.Context [65c01bc] This enables integration with Ginkgo 2.3.0's interruptible nodes and node timeouts.
• Eventually and Consistently that are passed a SpecContext can provide reports when an interrupt occurs [0d063c9]
• Eventually/Consistently will forward an attached context to functions that ask for one [e2091c5]
• Eventually/Consistently supports passing arguments to functions via WithArguments() [a2dc7c3]
• Eventually and Consistently can now be stopped early with StopTrying(message) and StopTrying(message).Now() [52976bb]

These improvements are all documented in Gomega's docs

Fixes

Maintenance

1.21.1

... (truncated)

Commits

• bf817a4 v1.23.0
• 7b8b801 fix broken call to Eventually
• ba35cc6 Allow ctx to be passed in as a leading parameter for Eventually and Consistently
• 818b78c AsyncAssertions emit the format.Object representation of the error when it i...
• d63d67e Rename AsyncSignalError to PollingSignalError
• abd25f0 fix go vet
• 618a133 Introduce TryAgainAfter
• 67ab22c Simplify StopTrying handling
• 75c8c70 Fix go vet and drop 1.17 from test matrix
• 237e97d Matchers can now return StopTrying() errors; StopTrying() can wrap an error t...
• 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)

[dependabot]

Superseded by #101.