chore(deps): bump cloud.google.com/go/bigquery from 1.74.0 to 1.76.0

[dependabot]

Bumps cloud.google.com/go/bigquery from 1.74.0 to 1.76.0.

Commits

• 243da70 chore(main): release spanner 1.76.0 (#11594)
• 0ee82ff perf(spanner): grab debug stack outside of lock (#11587)
• 4b40201 feat(spanner): support multiplexed session for read-write transactions & part...
• f2d581c chore(main): release auth 0.15.0 (#11613)
• 0d52ebd chore(all): update deps (#11601)
• 0e608bb feat(auth): Add hard-bound token request to compute token provider. (#11588)
• 798be26 chore(all): update Go to 1.24 (#11612)
• bd0aec1 feat(dlp): discovery of Vertex AI datasets (#11605)
• c08d347 feat(chat): Add DeletionType.SPACE_MEMBER. This is returned when a message se...
• 535f52e refactor(auth): refactor GetGRPCTransportCredsAndEndpoint return type to stru...
• Additional commits viewable 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)

[rhacs-bot]

A single node development cluster (infra-pr-1799) was allocated in production infra for this PR.

CI will attempt to deploy quay.io/rhacs-eng/infra-server: to it.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-1799 --zone us-central1-a --project acs-team-temp-dev

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️ Any clusters that you start using your dev infra instance should have a lifespan shorter then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance ceases to exist when the development cluster is deleted. ⚠️

Further Development

☕ If you make changes, you can commit and push and CI will take care of updating the development cluster.

🚀 If you only modify configuration (chart/infra-server/configuration) or templates (chart/infra-server/{static,templates}), you can get a faster update with:

make helm-deploy

Logs

Logs for the development infra depending on your @redhat.com authuser:

• authuser=0
• authuser=1
• authuser=2

Or:

kubectl -n infra logs -l app=infra-server --tail=1 -f