build(deps): bump google.golang.org/grpc from 1.79.2 to 1.79.3 in /network-agent#196
Merged
ls-ggg merged 1 commit intoMay 13, 2026
Conversation
Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.79.2 to 1.79.3. - [Release notes](https://github.com/grpc/grpc-go/releases) - [Commits](grpc/grpc-go@v1.79.2...v1.79.3) --- updated-dependencies: - dependency-name: google.golang.org/grpc dependency-version: 1.79.3 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
3 tasks
staryxchen
added a commit
that referenced
this pull request
May 12, 2026
Several workflows listen to both push and pull_request with overlapping
paths. When a PR head branch is pushed, GitHub fires both events, and
the existing concurrency keys cannot deduplicate them:
- build-check / build-envd-base-image group by github.ref, which
differs between push (refs/heads/<branch>) and pull_request
(refs/pull/N/merge);
- build-builder-image declares no concurrency block at all;
- hypervisor-integration explicitly includes ${{ github.event_name }}
in the concurrency key, which makes both runs coexist by design.
As a result, every check (Build CubeAPI, Build CubeMaster, ...) shows
up twice in the PR checks list, doubling CI cost for no benefit.
PR #195 and #196 are recent examples that triggered the duplicate
runs on Build Check.
Restrict the push trigger of the four affected workflows to the master
branch. PR validation now runs only via the pull_request event; direct
pushes to master remain covered.
Signed-off-by: staryxchen <staryxchen@tencent.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps google.golang.org/grpc from 1.79.2 to 1.79.3.
Release notes
Sourced from google.golang.org/grpc's releases.
Commits
dda86dbChange version to 1.79.3 (#8983)72186f1grpc: enforce strict path checking for incoming requests on the server (#8981)97ca352Changing version to 1.79.3-dev (#8954)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@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.