-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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 PRs require extra tidying #6795
Comments
Here's the command that was run: This confirms that |
Best if you raise a new issue here or @ me in the repo the next time you have a PR that looks wrong, and before you close it. |
Thank you for the speedy response and for looking into it! Got it. I'll close this and let you know the next time it happens (probably next Monday, as that's when updates are configured to happen). |
Reopening to track the current PR with this issue: GoogleCloudPlatform/golang-samples#1573 Thank you for the help with this! Let me know if there are any adjustments or anything I should try. |
Noting a few things: This repo doesn't just run Here's how it's run: Another point: the repo is running Go 1.14 on all Most likely solution: run I'm also wondering: why should we run |
Thank you for investigating!
Go 1.14 vs other versions could cause inconsistencies in Yes, you should run |
Renovate follows whatever Go version that is specified in the I'm thinking though that Renovate should ideally have a feature to "upgrade" that value anyway. Thanks for the clarification re |
Gotcha. I missed that. Often, the development version and the compatibility version are different. Is there any way we could specify the version of Go to use as part of the config? I'm not sure "upgrading" it is a good idea. That value indicates the minimum Go version needed to use the module. So, it's reasonable for it to stay the same for a long time. |
I wasn't aware that it means the minimum version - thank you for clarifying. In such case we may be better using the latest version of Go if that is also compatible. We also plan to allow configurable versions in the future but it's not supported yet |
Yes, I think latest would make the most sense. Sounds good with configuring. If it always used the latest, I don't think we'd need the ability to configure. |
Waiting on #6909 |
Friendly nudge -- looks like #6909 is fixed. |
Yes, I guess it's as simple as adding one more |
🎉 This issue has been resolved in version 22.19.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
I'll put this live tomorrow |
Thank you! |
Can you tick the rebase checkbox to try your existing PR again? |
Unfortunately, it looks like they still aren't |
It's rolled out. Here's the command that was run: |
When I check out that PR and run diff --git a/go.mod b/go.mod
index e60a1d4..0d6a58f 100644
--- a/go.mod
+++ b/go.mod
@@ -22,7 +22,6 @@ require (
github.com/fluent/fluent-logger-golang v1.5.0
github.com/go-sql-driver/mysql v1.5.0
github.com/gofrs/uuid v3.3.0+incompatible
- github.com/golang/groupcache v0.0.0-20200121045136-8c9f03a8e57e // indirect
github.com/golang/protobuf v1.4.2
github.com/gomodule/redigo v2.0.0+incompatible
github.com/google/go-cmp v0.5.1
diff --git a/go.sum b/go.sum
index 7ea2449..8566c1c 100644
--- a/go.sum
+++ b/go.sum
@@ -203,6 +203,7 @@ github.com/kr/pretty v0.1.0/go.mod h1:dAy3ld7l9f0ibDNOQOHHMYYIIbhfbHSm3C4ZsoJORN
github.com/kr/pty v1.1.1/go.mod h1:pFQYn66WHrOpPYNljwOMqo10TkYh1fy3cYio2l3bCsQ=
github.com/kr/text v0.1.0 h1:45sCR5RtlFHMR4UwH9sdQ5TC8v0qDQCHnXt+kaKSTVE=
github.com/kr/text v0.1.0/go.mod h1:4Jbv+DJW3UT/LiOwJeYQe1efqtUx/iVham/4vfdArNI=
+github.com/lib/pq v1.8.0 h1:9xohqzkUwzR4Ga4ivdTcawVS89YSDVxXMa3xJX3cGzg=
github.com/lib/pq v1.8.0/go.mod h1:AlVN5x4E4T544tWzH6hKfbfQvm3HdbOxrmggDNAPY9o=
github.com/linkedin/goavro/v2 v2.9.8 h1:jN50elxBsGBDGVDEKqUlDuU1cFwJ11K/yrJCBMe/7Wg=
github.com/linkedin/goavro/v2 v2.9.8/go.mod h1:UgQUb2N/pmueQYH9bfqFioWxzYCZXSfF8Jw03O5sjqA= Surely we don't need another tidy? |
Something else that is perhaps contributing is that we're not actually running the |
That command looks OK to me. I was concerned about the working directory because Each I tried running the I don't think we need the |
Im also facing a similar issue
Running
|
Not the same issue, please see if you can reproduce it in a public repo and raise a separate bug report. |
Commands: go get -u -d -t ./... go mod tidy Renovate still seems to have trouble with Go modules: renovatebot/renovate#6795
Commands: go get -u -d -t ./... go mod tidy Renovate still seems to have trouble with Go modules: renovatebot/renovate#6795
Closing this issue as it's a duplicate of #6213. |
Which Renovate are you using?
WhiteSource Renovate App (the forking version)
Which platform are you using?
GitHub.com
Have you checked the logs? Don't forget to include them if relevant
No.
What would you like to do?
Have
go mod tidy
run when making dependency updates. For example, GoogleCloudPlatform/golang-samples#1556 required me updating the PR manually to rungo mod tidy
on all modules.I do have
postUpdateOptions.gomodTidy
configured, but maybe it's not configured correctly? https://github.com/GoogleCloudPlatform/golang-samples/blob/2c581f8b444a3b4cf790d4350ea212d1d9c0f8d0/.github/renovate.json#L7-L9The text was updated successfully, but these errors were encountered: