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

   ## Summary
   
   The Renovate dependency dashboard reports:
   
   > Failed to look up go package `github.com/golangci/golangci-lint/v2`: 
no-result. Files affected: `Makefile`
   
   so golangci-lint version bumps are being missed. The Makefile annotation is 
correct for the `go` datasource, and that datasource resolves fine for every 
other Go-installed tool here (`kustomize/v5`, `controller-tools`, 
`crd-ref-docs`, `helm-docs`, `x/vuln`) — the failure is specific to 
golangci-lint, which is a long-standing problem case for the Go module-proxy 
lookup and tends to persist rather than clear on its own.
   
   ## Change
   
   Track golangci-lint via the `github-releases` datasource against 
`golangci/golangci-lint`, which reads the GitHub release tags (`v2.12.2`, …) 
directly — the same approach already used for `operator-sdk` and `rumdl`:
   
   ```make
   -# renovate: datasource=go depName=github.com/golangci/golangci-lint/v2
   +# renovate: datasource=github-releases depName=golangci/golangci-lint
    GOLANGCI_LINT_VERSION ?= v2.12.2
   ```
   
   The `go install 
github.com/golangci/golangci-lint/v2/cmd/golangci-lint@$(GOLANGCI_LINT_VERSION)`
 recipe is unchanged; only the version-discovery datasource changes.
   
   ## Testing
   
   - `make lint-go` still resolves and runs golangci-lint (v2.12.2) clean
   - Version discovery is verifiable once merged: the dashboard error should 
clear and golangci-lint should resume getting update PRs
   
   ---
   Opened as a draft.


-- 
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