build(deps): bump google.golang.org/grpc from 1.83.0 to 1.83.1

[dependabot]

Bumps google.golang.org/grpc from 1.83.0 to 1.83.1.

Release notes

Sourced from google.golang.org/grpc's releases.

Release 1.83.1

Security

• xds/rbac: Fix a bug where nested Principal or Permission rules with :scheme or grpc- prefixed header matchers were not rejected, which could cause DENY rules to fail open. (#9258)
  • Special Thanks: @​nvxbug
• xds/rbac: Fix a bug where the host header matcher was not being replaced with :authority in nested Principal or Permission rules. (#9258)
  • Special Thanks: @​nvxbug
• xds/rbac: Fix a bug where a header matcher whose name was not lowercase, such as X-Role, matched no header, which could cause DENY rules to fail open. (#9332)
  • Special Thanks: @​alimony
• xds/rbac: Fix a bug where a :scheme or grpc- prefixed header matcher was accepted when its name was not lowercase. (#9332)
  • Special Thanks: @​alimony
• xds/rbac: Fix a bug where a Host header matcher was not replaced with :authority. (#9332)
  • Special Thanks: @​alimony

Performance

• transport: Restrict memory overhead of buffering small data frames. (#9331)

Commits

• 1550d9e Change version to 1.83.1 (#9336)
• ebba6f3 Cherry-pick #9258 and #9332 into v1.83.x (#9335)
• 8cfeca0 Cherry-pick #9331 to v1.83.x (#9333)
• dec6951 Change version to 1.83.1-dev (#9229)
• See full diff 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[mergify]

This pull request does not have a backport label. Could you fix it @dependabot[bot]? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-./d./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[github-actions]

TL;DR

check-ci failed because the dependency update changed go.mod/go.sum at the repo root and testing/go.mod/testing/go.sum, but the dependency graph is not fully tidied for all module contexts. The immediate fix is to run module tidy in both modules and commit any resulting lockfile changes.

Remediation

• Run go mod tidy in the repository root and in testing/ (or use the project’s dependency-maintenance target that does this for both modules), then commit updated go.mod/go.sum files.
• Re-run CI (.buildkite/scripts/check_ci.sh) to confirm the module files are clean.

Investigation details

Root Cause

Buildkite fails in dependency consistency checks with:

• go: updates to go.mod needed; to update it: go mod tidy

This indicates the submitted module file changes are incomplete for at least one package/test resolution path used by CI. Given this PR updates both top-level and testing/ module files, the failure is a dependency issue (module graph/lockfile drift), not an application code bug.

Evidence

• Build: https://buildkite.com/elastic/fleet-server/builds/16594
• Job/step: Run check-ci (.buildkite/scripts/check_ci.sh)
• Key log excerpt:

  go: updates to go.mod needed; to update it:
      go mod tidy
  

• PR files touched include:
  • go.mod, go.sum
  • testing/go.mod, testing/go.sum

Verification

• Not run locally in this workflow; conclusion is from the Buildkite failure output and changed file set.

Follow-up

If tidy is run in both modules and no diffs remain, this Buildkite failure should clear on retry.

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[github-actions]

@Mergifyio backport 9.5 9.4 8.19

[mergify]

backport 9.5 9.4 8.19

✅ Backports have been created

Details

• #7752 [9.5](backport #7748) build(deps): bump google.golang.org/grpc from 1.83.0 to 1.83.1 has been created for branch 9.5
• #7753 [9.4](backport #7748) build(deps): bump google.golang.org/grpc from 1.83.0 to 1.83.1 has been created for branch 9.4
• #7754 [8.19](backport #7748) build(deps): bump google.golang.org/grpc from 1.83.0 to 1.83.1 has been created for branch 8.19