[9.4](backport #7748) build(deps): bump google.golang.org/grpc from 1.83.0 to 1.83.1

[mergify]

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.

---

This is an automatic backport of pull request #7748 done by [Mergify](https://mergify.com).

[github-actions]

TL;DR

This Buildkite failure is an infrastructure/bootstrap failure, not a code regression from this PR: both failed jobs broke while setting up Go because the downloaded gvm binary was actually a 504 Gateway Time-out HTML page. Immediate action is to re-run the failed jobs; longer-term, harden the download check in CI bootstrap.

Remediation

• Re-run the failed Buildkite jobs for build https://buildkite.com/elastic/fleet-server/builds/17016 (Run check-ci and Detect FIPS crypto imports).
• Harden .buildkite/scripts/common.sh in with_go() by changing the curl invocation at .buildkite/scripts/common.sh:46 to fail on HTTP errors (for example curl --fail --show-error --silent --location) and validate the downloaded artifact before executing it.

Investigation details

Root Cause

Both failing steps call with_go() from .buildkite/scripts/common.sh, which downloads gvm and executes it:

• .buildkite/scripts/common.sh:46 downloads ${WORKSPACE}/gvm via curl -sL.
• .buildkite/scripts/common.sh:48-49 executes gvm and then go version.

In this build, the downloaded file content was HTML (<h1>504 Gateway Time-out</h1>), so executing gvm failed with a shell syntax error and go was never installed (go: command not found). This is consistent with a transient upstream/network fetch failure plus missing strict HTTP failure handling in the bootstrap script.

Evidence

• Build: https://buildkite.com/elastic/fleet-server/builds/17016
• Jobs/steps: Run check-ci (.buildkite/scripts/check_ci.sh) and Detect FIPS crypto imports (.buildkite/scripts/check_detect_fips_crypto.sh)
• Key log excerpts:

.../bin/gvm: line 1: `<html><body><h1>504 Gateway Time-out</h1>'
.buildkite/scripts/common.sh: line 49: go: command not found

PR scope is dependency-only (go.mod, go.sum, testing/go.mod, testing/go.sum, NOTICE files), with no CI script changes.

Verification

• Local reruns were not performed in this workflow; analysis is based on provided Buildkite logs and PR diff/metadata.

Follow-up

• I checked for existing flaky-test issues related to this failure mode and found none matching this gvm 504 bootstrap error.

---

What is this? | From workflow: Observability Agentic Workflow — Status

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