Bump github.com/onsi/gomega from 1.10.2 to 1.17.0

[dependabot]

Bumps github.com/onsi/gomega from 1.10.2 to 1.17.0.

Release notes

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

v1.17.0

1.17.0

Features

• Add HaveField matcher [3a26311]
• add Error() assertions on the final error value of multi-return values (#480) [2f96943]
• separate out offsets and timeouts (#478) [18a4723]
• fix transformation error reporting (#479) [e001fab]
• allow transform functions to report errors (#472) [bf93408]

Fixes

Stop using deprecated ioutil package (#467) [07f405d]

v1.16.0

Features

• feat: HaveHTTPStatus multiple expected values (#465) [aa69f1b]
• feat: HaveHTTPHeaderWithValue() matcher (#463) [dd83a96]
• feat: HaveHTTPBody matcher (#462) [504e1f2]
• feat: formatter for HTTP responses (#461) [e5b3157]

v1.15.0

1.15.0

Fixes

The previous version (1.14.0) introduced a change to allow Eventually and Consistently to support functions that make assertions. This was accomplished by overriding the global fail handler when running the callbacks passed to Eventually/Consistently in order to capture any resulting errors. Issue #457 uncovered a flaw with this approach: when multiple Eventuallys are running concurrently they race when overriding the singleton global fail handler.

1.15.0 resolves this by requiring users who want to make assertions in Eventually/Consistently call backs to explicitly pass in a function that takes a Gomega as an argument. The passed-in Gomega instance can be used to make assertions. Any failures will cause Eventually to retry the callback. This cleaner interface avoids the issue of swapping out globals but comes at the cost of changing the contract introduced in v1.14.0. As such 1.15.0 introduces a breaking change with respect to 1.14.0 - however we expect that adoption of this feature in 1.14.0 remains limited.

In addition, 1.15.0 cleans up some of Gomega's internals. Most users shouldn't notice any differences stemming from the refactoring that was made.

v1.14.0

1.14.0

Features

• gmeasure.SamplingConfig now suppers a MinSamplingInterval [e94dbca]
• Eventually and Consistently support functions that make assertions [2f04e6e]
  • Eventually and Consistently now allow their passed-in functions to make assertions. These assertions must pass or the function is considered to have failed and is retried.
  • Eventually and Consistently can now take functions with no return values. These implicitly return nil if they contain no failed assertion. Otherwise they return an error wrapping the first assertion failure. This allows these functions to be used with the Succeed() matcher.
  • Introduce InterceptGomegaFailure - an analogue to InterceptGomegaFailures - that captures the first assertion failure and halts execution in its passed-in callback.

Fixes

• Call Verify GHTTPWithGomega receiver funcs (#454) [496e6fd]
• Build a binary with an expected name (#446) [7356360]

v1.13.0

• Set consistently and eventually defaults on init (#443)

... (truncated)

Changelog

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

1.17.0

Features

• Add HaveField matcher [3a26311]
• add Error() assertions on the final error value of multi-return values (#480) [2f96943]
• separate out offsets and timeouts (#478) [18a4723]
• fix transformation error reporting (#479) [e001fab]
• allow transform functions to report errors (#472) [bf93408]

Fixes

Stop using deprecated ioutil package (#467) [07f405d]

1.16.0

Features

• feat: HaveHTTPStatus multiple expected values (#465) [aa69f1b]
• feat: HaveHTTPHeaderWithValue() matcher (#463) [dd83a96]
• feat: HaveHTTPBody matcher (#462) [504e1f2]
• feat: formatter for HTTP responses (#461) [e5b3157]

1.15.0

Fixes

The previous version (1.14.0) introduced a change to allow Eventually and Consistently to support functions that make assertions. This was accomplished by overriding the global fail handler when running the callbacks passed to Eventually/Consistently in order to capture any resulting errors. Issue #457 uncovered a flaw with this approach: when multiple Eventuallys are running concurrently they race when overriding the singleton global fail handler.

1.15.0 resolves this by requiring users who want to make assertions in Eventually/Consistently call backs to explicitly pass in a function that takes a Gomega as an argument. The passed-in Gomega instance can be used to make assertions. Any failures will cause Eventually to retry the callback. This cleaner interface avoids the issue of swapping out globals but comes at the cost of changing the contract introduced in v1.14.0. As such 1.15.0 introduces a breaking change with respect to 1.14.0 - however we expect that adoption of this feature in 1.14.0 remains limited.

In addition, 1.15.0 cleans up some of Gomega's internals. Most users shouldn't notice any differences stemming from the refactoring that was made.

1.14.0

Features

• gmeasure.SamplingConfig now suppers a MinSamplingInterval [e94dbca]
• Eventually and Consistently support functions that make assertions [2f04e6e]
  • Eventually and Consistently now allow their passed-in functions to make assertions. These assertions must pass or the function is considered to have failed and is retried.
  • Eventually and Consistently can now take functions with no return values. These implicitly return nil if they contain no failed assertion. Otherwise they return an error wrapping the first assertion failure. This allows these functions to be used with the Succeed() matcher.
  • Introduce InterceptGomegaFailure - an analogue to InterceptGomegaFailures - that captures the first assertion failure and halts execution in its passed-in callback.

Fixes

• Call Verify GHTTPWithGomega receiver funcs (#454) [496e6fd]
• Build a binary with an expected name (#446) [7356360]

1.13.0

Features

• gmeasure provides BETA support for benchmarking (#447) [8f2dfbf]

... (truncated)

Commits

• 05f6097 v1.17.0
• 3a26311 Add HaveField matcher
• 2f96943 add Error() assertions on the final error value of multi-return values (#480)
• 18a4723 separate out offsets and timeouts (#478)
• e001fab fix transformation error reporting (#479)
• 61cd3b8 Fix typo (#477)
• bf93408 allow transform functions to report errors (#472)
• 07f405d chore: stop using deprecated ioutil package (#467)
• afd6b76 v1.16.0
• aa69f1b feat: HaveHTTPStatus multiple expected values (#465)
• 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)