build(deps): bump golang.org/x/net from 0.7.0 to 0.17.0 #317
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.7.0 to 0.17.0. - [Commits](golang/net@v0.7.0...v0.17.0) --- updated-dependencies: - dependency-name: golang.org/x/net dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
the
dependencies
|
@anoopcs9 this isn't being automerged due to the lack of success for |
|
/test centos-ci/sink-clustered/mini-k8s-latest |
Hm, I'm wondering why automatic trigger didn't kick in 🤷🏻 . For now I have initiated a run with our usual GitHub comment. |
dependabot
bot
deleted the
dependabot/go_modules/golang.org/x/net-0.17.0
branch
I was just thinking about this and I bet that it is because this PR is automatically filed by dependabot. It treats dependabot as an non-admin user according to: We either need to remember to manually add the comment like you did OR add dependabot to this of PR submitters that automatically have the job run. Adding it to the list as an "admin" feels a bit weird to me tho. But I'll defer to your better knowledge of centosci if that's not a big deal. |
You are spot on.
Yeah..
Let's continue with the manual intervention which I guess is only required in a monthly fashion(if any). |
Bumps golang.org/x/net from 0.7.0 to 0.17.0.
Commits
b225e7chttp2: limit maximum handler goroutines to MaxConcurrentStreams88194adgo.mod: update golang.org/x dependencies2b60a61quic: fix several bugs in flow control accounting73d82efquic: handle DATA_BLOCKED frames5d5a036quic: handle streams moving from the data queue to the meta queue350aad2quic: correctly extend peer's flow control window after MAX_DATA21814e7quic: validate connection id transport parametersa600b35quic: avoid redundant MAX_DATA updatesea63359http2: check stream body is present on read timeoutddd8598quic: version negotiationDependabot 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.