Bump the github-google group across 1 directory with 3 updates

[dependabot]

Bumps the github-google group with 2 updates in the / directory: github.com/googleapis/gax-go/v2 and github.com/google/gnostic.

Updates github.com/googleapis/gax-go/v2 from 2.14.1 to 2.15.0

Release notes

Sourced from github.com/googleapis/gax-go/v2's releases.

v2.15.0

2.15.0 (2025-07-09)

Features

• apierror: improve gRPC status code mapping for HTTP errors (#431) (c207f2a)

v2.14.2

2.14.2 (2025-05-12)

Documentation

• v2: Fix Backoff doc to accurately explain Multiplier (#423) (16d1791), refs #422

Commits

• cb08006 chore(main): release 2.15.0 (#433)
• c207f2a feat(apierror): improve gRPC status code mapping for HTTP errors (#431)
• 7025124 chore(all): update all (#430)
• 9b083b5 chore(all): update all (#429)
• c2be0a9 chore(all): update all (#427)
• d9212e7 chore(all): update all (#426)
• 4938a10 chore(main): release 2.14.2 (#424)
• df6582b chore(all): update all (#425)
• 16d1791 docs(v2): Fix Backoff doc to accurately explain Multiplier (#423)
• fef87e6 chore(all): update all (#421)
• Additional commits viewable in compare view

Updates github.com/google/gnostic from 0.7.0 to 0.7.1

Commits

• 39aedcf chore: migrate from gopkg.in/yaml.v3 to go.yaml.in/yaml/v3 (#454)
• ad271d5 feat: handle escape and null value (#419)
• fe4fc1e plugins/gnostic-analyze/summarize: fix dropped error (#426)
• bf7795e metrics/vocabulary: err check before Close() (#425)
• f702249 generate-gnostic: fix dropped errors (#415)
• da1adca Fix typos in README.md (#423)
• See full diff in compare view

Updates github.com/google/gnostic-models from 0.6.9 to 0.7.0

Commits

• 82b4ba0 Fix go.mod
• 1214835 update yaml library to go.yaml.in/yaml
• 511df6b update README to 2025
• fbe822a Update README to 2024
• d9cde49 chore: omit comparison to bool constant
• 8f45726 chore: unnecessary use of fmt.Sprintf
• d47ab80 add manual trigger github actions
• 164b47f Disable protoc download in CI
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[k8s-ci-robot]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign msau42 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

[k8s-ci-robot]

@dependabot[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-gcp-filestore-csi-driver-unit	9098e49	link	true	/test pull-gcp-filestore-csi-driver-unit
pull-gcp-filestore-csi-driver-sanity	9098e49	link	true	/test pull-gcp-filestore-csi-driver-sanity
pull-gcp-filestore-csi-driver-verify	9098e49	link	true	/test pull-gcp-filestore-csi-driver-verify
pull-gcp-filestore-csi-driver-kubernetes-integration	9098e49	link	true	/test pull-gcp-filestore-csi-driver-kubernetes-integration
pull-gcp-filestore-csi-driver-e2e	9098e49	link	true	/test pull-gcp-filestore-csi-driver-e2e

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.