search

kubevirt / kubevirt-velero-plugin

Plugin to Velero which automates backing up and restoring KubeVirt/CDI objects
Apache License 2.0
29 stars 28 forks source link

Bump github.com/onsi/gomega from 1.20.2 to 1.22.1 #93

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps github.com/onsi/gomega from 1.20.2 to 1.22.1.

Release notes

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

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

  • Eventually and Consistently that are passed a SpecContext can provide reports when an interrupt occurs [0d063c9]

v1.21.0

1.21.0

Features

  • Eventually and Consistently can take a context.Context [65c01bc] This enables integration with Ginkgo 2.3.0's interruptible nodes and node timeouts.
  • Introduces Eventually.Within.ProbeEvery with tests and documentation (#591) [f633800]
  • New BeKeyOf matcher with documentation and unit tests (#590) [fb586b3]

Fixes

  • Cover the entire gmeasure suite with leak detection [8c54344]
  • Fix gmeasure leak [119d4ce]
  • Ignore new Ginkgo ProgressSignal goroutine in gleak [ba548e2]

Maintenance

  • Fixes crashes on newer Ruby 3 installations by upgrading github-pages gem dependency (#596) [12469a0]
Changelog

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

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

Features

  • Eventually and Consistently that are passed a SpecContext can provide reports when an interrupt occurs [0d063c9]

1.21.0

Features

  • Eventually and Consistently can take a context.Context [65c01bc] This enables integration with Ginkgo 2.3.0's interruptible nodes and node timeouts.
  • Introduces Eventually.Within.ProbeEvery with tests and documentation (#591) [f633800]
  • New BeKeyOf matcher with documentation and unit tests (#590) [fb586b3]

Fixes

  • Cover the entire gmeasure suite with leak detection [8c54344]
  • Fix gmeasure leak [119d4ce]
  • Ignore new Ginkgo ProgressSignal goroutine in gleak [ba548e2]

Maintenance

  • Fixes crashes on newer Ruby 3 installations by upgrading github-pages gem dependency (#596) [12469a0]
Commits
  • 40d0cc9 v1.22.1
  • e5105cf When passed a context and no explicit timeout, Eventually will only timeout w...
  • bf3cba9 Allow StopTrying() to be wrapped
  • c5d5c39 bump to ginkgo v2.3.0
  • 8916066 v1.22.0
  • aeab53a fix go vet issue
  • 52976bb Eventually an Consistently can now be stopped early with StopTrying(message) ...
  • a2dc7c3 Gomega supports passing arguments to functions via WithArguments()
  • e2091c5 Eventually/Consistently will forward an attached context to functions that as...
  • 2e34979 v1.21.1
  • Additional commits viewable 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 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)
kubevirt-bot commented 1 year ago

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a kubevirt member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
brybacki commented 1 year ago

/ok-to-test

brybacki commented 1 year ago

/test pull-kvp-functional-test

brybacki commented 1 year ago

/lgtm /approve

kubevirt-bot commented 1 year ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: brybacki

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/kubevirt/kubevirt-velero-plugin/blob/main/OWNERS)~~ [brybacki] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment