villebro opened a new pull request, #306:
URL: https://github.com/apache/superset-kubernetes-operator/pull/306

   ## Summary
   
   PR #299 bumped the `golang` builder image to `1.27.0`, but the go.mod `go`
   directive stayed at `1.26.6`. Because Go's language level is gated by the
   `go` directive (not the toolchain that compiles it), the release image built
   with 1.27 while the language level — and CI, which resolves `go-version-file:
   go.mod` — remained on 1.26. This bumps the directive to `1.27.0` so the
   language level, CI, and the builder/devcontainer images are all aligned on
   1.27, and fixes the Renovate config so the directive never drifts again.
   
   The drift was not intentional: #295 grouped the three golang pins with the
   stated intent that "1.27 will come through later as a grouped bump." It
   didn't, because Renovate parses the `go` directive with `go-mod-directive`
   versioning, treating `go 1.26.6` as a `>=1.26.6` minimum constraint. Under
   the default `replace` rangeStrategy, a range is only rewritten when the new
   version falls outside it — every newer Go still satisfied `>=1.26.6`, so the
   directive never moved while the exact-pinned image tags advanced freely.
   
   ## Details
   
   - **go.mod**: `go 1.26.6` → `go 1.27.0` (no `toolchain` directive — 1.27
     throughout). `go mod tidy` is a no-op; `go build`, `go vet`, the unit
     tests, and `golangci-lint` all pass under Go 1.27.
   - **renovate.json**: add a rule scoping `rangeStrategy: bump` to the `go`
     directive (`matchManagers: ["gomod"], matchDepNames: ["go"]`). `bump`
     raises the constraint to the latest satisfying version even when the range
     still matches, so a Go release lifts the directive in lockstep. The rule
     sets only `rangeStrategy` — no `groupName` — so the directive rides in the
     existing "Go toolchain" group PR alongside the Dockerfile and devcontainer
     image bumps.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to