You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Command failed: go get -d -t ./...
go: github.com/imdario/mergo@v1.0.0: parsing go.mod:
module declares its path as: dario.cat/mergo
but was required as: github.com/imdario/mergo
Command failed: go get -d -t ./...
go: gopkg.in/go-playground/webhooks.v6@v6.3.0: parsing go.mod:
module declares its path as: github.com/go-playground/webhooks/v6
but was required as: gopkg.in/go-playground/webhooks.v6
The text was updated successfully, but these errors were encountered:
This is a very specific issue: a dependency changing its module name. IMO these cases are best handled manually.
Now the question is, should a PR be created for this or not? Given that this is configurable via prCreation, I think each team can use whatever option it works best for them. So to avoid noise from failing PRs a team can change their .github/renovate.json to contain: "prCreation": "status-success".
But by default, I think we should continue to open those PRs so at least teams know that there is a dependency to be updated and it contains breaking changes, however they will need to manually create a superseding PR for it.
We had at least two go mod bump prs by renovate where renovate itself realized that there was an issue but still created them.
rancher/fleet#2304
rancher/fleet#2305
The text was updated successfully, but these errors were encountered: