-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
go.mod 1.19 update failed with cryptic error message before the go docker image was updated #16933
Comments
@SuperSandro2000 Something went wrong when you copy/pasted your logs, the Have you created a minimal reproduction repository? section is included in the logs toggle. Please edit your post so it displays the missing section again. 😉 Edit: this issue seems related: |
Forgot a line break at the end of the logs. We are fine with the go version being updated but the error message was not helpful and the process should be improved for future new go versions. |
since your
is the issue only related to the message inside |
If the user has added constraints for go then this is by design and not a bug |
Yes but good reminder. I wonder why the update was attempted in the first place. |
🎉 This issue has been resolved in version 32.144.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
How are you running Renovate?
Mend Renovate hosted app on github.com
Was this something which used to work for you, and then stopped?
It used to work, and then stopped
Describe the bug
The go.mod update from 1.18 to 1.19 failed in sapcc/keppel#107 because renovate bot was still using a go 1.18 docker image
docker.io/renovate/go:1.18.5
.The exact detail can be found in the log
go: go.mod file indicates go 1.19, but maximum version supported by tidy is 1.18
but on the PR only a very genericProcess exited with exit code "1"
error was logged.Relevant debug logs
Logs
Have you created a minimal reproduction repository?
No reproduction, but I have linked to a public repo where it occurs
The text was updated successfully, but these errors were encountered: