cloud-provider-gcp-cloud-controller-manager/35.0.0 package update

[octo-sts]

Commit: 5efae2d228b66db5478bee2fba8a3dccd18c8a5b

Note: If you need to make manual changes to this PR, apply the skip:staging-update-bot label so the reconciler won't overwrite them.

[octo-sts]

🔢 Build Failed: Dependency Version Mismatch

go: module . listed in go.work file requires go >= 1.25.5, but go.work lists go 1.24.0; to update it: go work use

Build Details

Category	Details
Build System	Go
Failure Point	go get command during go/bump step

Root Cause Analysis 🔍

Version mismatch between the Go version required by the module (>= 1.25.5) and the version specified in go.work file (1.24.0). The go.work file needs to be updated to match the current Go runtime version.

---

🔍 Build failure fix suggestions

Found similar build failures that have been fixed in the past and analyzed them to suggest a fix:

Similar PRs with fixes

• k3d/5.8.3-r15: cve remediation #63357

Suggested Changes

File: cloud-provider-gcp-cloud-controller-manager.yaml

• addition (After the first go/bump step (around line 19))
  Original:

  - uses: go/bump
    with:
      deps: |-
        golang.org/x/crypto@v0.45.0
      modroot: providers

Replacement:

  - uses: go/bump
    with:
      deps: |-
        golang.org/x/crypto@v0.45.0
      modroot: providers
      work: true

  - runs: |
      go work use

Content:

Add a new pipeline step to run 'go work use' command

Click to expand fix analysis

Analysis

Looking at the similar fixed build failures, I can identify a clear pattern: all three cases involved Go modules requiring a newer version of Go (>= 1.25.0 or >= 1.25.5) than what was specified in the go.work file. The primary fix pattern is to run go work use command to update the go.work file to match the current Go runtime version. In Fix Example #0, this was done by adding a runs: | go work use step after the go/bump step. Additionally, some fixes included enabling workspace mode with work: true and adjusting tidy settings with skip-initial-tidy: true. The current failure shows the same root cause: module requires go >= 1.25.5 but go.work lists go 1.24.0.

Click to expand fix explanation

Explanation

This fix addresses the root cause of the build failure by updating the go.work file to match the current Go runtime version. The error occurs because the module requires Go >= 1.25.5 but the go.work file specifies Go 1.24.0. By adding work: true to the go/bump step, we enable workspace mode, and then running go work use updates the go.work file to use the current Go version available in the build environment. This pattern was successfully used in Fix Example #0 for the same type of error. The go work use command automatically detects and updates the Go version in the workspace file to match the runtime, resolving the version mismatch that's causing the build to fail.

Click to expand alternative approaches

Alternative Approaches

• Add the go work use command after each go/bump step instead of just the first one
• Set skip-initial-tidy: true in the go/bump steps to avoid tidy conflicts during the workspace update
• Use a global runs step at the beginning of the pipeline to update the workspace before any go/bump operations

---

Was this comment helpful? Please use 👍 or 👎 reactions on this comment.