chore(all): update deps (major)

[renovate-bot]

This PR contains the following updates:

Package	Type	Update	Change
actions/cache	action	major	v5 → v6
actions/checkout	action	major	v6 → v7
bazel		major	8.8.0 → 9.2.0

---

Release Notes

actions/cache (actions/cache)

v6.1.0

Compare Source

What's Changed

• Bump @​actions/cache to v6.1.0 - handle read-only cache access by @​jasongin in #​1768

Full Changelog: actions/cache@v6...v6.1.0

v6.0.0

Compare Source

What's Changed

• Update packages, migrate to ESM by @​Samirat in #​1760

Full Changelog: actions/cache@v5...v6.0.0

actions/checkout (actions/checkout)

v7.0.1

Compare Source

• Bump github/codeql-action from 3 to 4 by @​dependabot[bot] in #​2475
• Bump actions/setup-node from 4 to 6 by @​dependabot[bot] in #​2477
• Bump docker/build-push-action from 6.5.0 to 7.2.0 by @​dependabot[bot] in #​2478
• Bump docker/login-action from 3.3.0 to 4.2.0 by @​dependabot[bot] in #​2479
• Bump actions/checkout from 6 to 7 by @​dependabot[bot] in #​2488
• Bump actions/upload-artifact from 4 to 7 by @​dependabot[bot] in #​2476
• eslint 9 by @​dependabot[bot] in #​2474
• Bump the minor-actions-dependencies group with 2 updates by @​dependabot[bot] in #​2499
• skip running unsafe pr check if input is default by @​aiqiaoy in #​2518
• trim only ascii whitespace for branch by @​aiqiaoy in #​2521
• escape values passed to --unset by @​aiqiaoy in #​2530

v7.0.0

Compare Source

• Block checking out fork PR for pull_request_target and workflow_run by @​aiqiaoy in #​2454
• Bump actions/publish-immutable-action from 0.0.3 to 0.0.4 in the minor-actions-dependencies group across 1 directory by @​dependabot[bot] in #​2458
• Bump flatted from 3.3.1 to 3.4.2 by @​dependabot[bot] in #​2460
• Bump js-yaml from 4.1.0 to 4.2.0 by @​dependabot[bot] in #​2461
• Bump @​actions/core and @​actions/tool-cache and Remove uuid by @​dependabot[bot] in #​2459
• upgrade module to esm and update dependencies by @​aiqiaoy in #​2463
• Bump the minor-npm-dependencies group across 1 directory with 3 updates by @​dependabot[bot] in #​2462

bazelbuild/bazel (bazel)

v9.2.0

Compare Source

Release Notes:

v9.1.1

Compare Source

Release Notes:

v9.1.0

Compare Source

Release Notes:

v9.0.2

Compare Source

Release Notes:

v9.0.1

Compare Source

Release Notes:

v9.0.0

Compare Source

Release Notes:

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Monday through Friday (* * * * 1-5)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[morrowc]

CI Failure Analysis & Proposed Fix for PR #280

Root Cause

The CI build failed during bazel build //... with:

ERROR: Traceback (most recent call last):
	File ".../external/openconfig_gnmi+/bazel/generate_cc.bzl", line 195, column 29, in <toplevel>
		"plugin": attr.label(
Error in label: at index 0 of providers, got element of type string, want sequence
ERROR: error loading package '@@openconfig_gnmi+//proto/gnmi': at .../external/openconfig_gnmi+/bazel/cc_grpc_library.bzl:21:6: initialization of module 'bazel/generate_cc.bzl' failed
ERROR: /var/tmp/gnsi/pathz/BUILD.bazel:9:14: error loading package '@@openconfig_gnmi+//proto/gnmi' ... referenced by '//pathz:pathz_proto'

• Why it failed: Bazel 9 dropped support for legacy string provider names in rule attribute definitions (e.g. providers = ["files_to_run"]).
• Where it comes from: The dependency openconfig_gnmi 0.14.1 (the latest release on BCR) contains legacy bazel/generate_cc.bzl that declares providers = ["files_to_run"].
• Upstream status: In the openconfig/gnmi repository, commit 833747e39f20b3a5b4da786ae0782ca971bd7c83 already deleted bazel/generate_cc.bzl and switched to @com_github_grpc_grpc//bazel:cc_grpc_library.bzl. However, no release tag newer than v0.14.1 has been published to BCR yet.

---

Proposed Fixes

Option 1: Keep Bazel at 8.8.0 for now (Recommended)

Revert .bazelversion back to 8.8.0 in this PR (allowing the GitHub Actions upgrades actions/checkout@v7 and actions/cache@v6 to proceed and pass). Bazel 9 can then be adopted once a new release of openconfig/gnmi is published to BCR.

To prevent Renovate from re-bumping Bazel to 9.x until gnmi is ready, .github/renovate.json can be configured with:

{
  "packageRules": [
    {
      "matchPackageNames": ["bazelbuild/bazel", "bazel"],
      "allowedVersions": "<9.0.0"
    }
  ]
}

Option 2: Use git_override in MODULE.bazel to support Bazel 9.2.0 immediately

If we want to proceed with Bazel 9.2.0 immediately, add a git_override for openconfig_gnmi in MODULE.bazel to point to a commit on master:

git_override(
    module_name = "openconfig_gnmi",
    remote = "https://github.com/openconfig/gnmi.git",
    commit = "a4e40e60426e5b30ce29fd8115809d2dbe47584f",
)

(Also bump protobuf to 35.1 in MODULE.bazel to match the version required by grpc.)

Verification: Verified locally that with this override, Bazel 9.2.0 builds all 42 targets and all tests pass cleanly.

Option 3: Cut an upstream release of openconfig/gnmi

Tag v0.14.2 (or v0.15.0) on openconfig/gnmi, publish it to BCR, and update MODULE.bazel to point to the new release.