Bump golang.org/x/crypto from 0.21.0 to 0.31.0 in /.ibm/tools/tests-results #7276
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
dependencies
openshift-ci
bot
added
the
needs-ok-to-test
|
Hi @dependabot[bot]. Thanks for your PR. I'm waiting for a redhat-developer member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
✅ Deploy Preview for odo-docusaurus-preview canceled.
|
|
/ok-to-test |
openshift-ci
bot
added
ok-to-test
|
@dependabot rebase |
dependabot
bot
force-pushed
the
dependabot/go_modules/dot-ibm/tools/tests-results/golang.org/x/crypto-0.31.0
branch
from
fe8fe69 to
a97e1d2
Compare
|
|
|
@dependabot recreate |
Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.21.0 to 0.31.0. - [Commits](golang/crypto@v0.21.0...v0.31.0) --- updated-dependencies: - dependency-name: golang.org/x/crypto dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/go_modules/dot-ibm/tools/tests-results/golang.org/x/crypto-0.31.0
branch
from
95e5ef0 to
755f130
Compare
|
|
@rm3l: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
openshift-ci
bot
added
the
lgtm
rm3l
deleted the
dependabot/go_modules/dot-ibm/tools/tests-results/golang.org/x/crypto-0.31.0
branch
Bumps golang.org/x/crypto from 0.21.0 to 0.31.0.
Commits
b4f1988ssh: make the public key cache a 1-entry FIFO cache7042ebcopenpgp/clearsign: just use rand.Reader in tests3e90321go.mod: update golang.org/x dependencies8c4e668x509roots/fallback: update bundle6018723go.mod: update golang.org/x dependencies71ed71bREADME: don't recommend go get750a45fsha3: add MarshalBinary, AppendBinary, and UnmarshalBinary36b1725sha3: avoid trailing permutation80ea76esha3: fix padding for long cSHAKE parametersc17aa50sha3: avoid buffer copyDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.