-
Notifications
You must be signed in to change notification settings - Fork 12.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
Chore: Upgrade Go to 1.20.10 #76355
Chore: Upgrade Go to 1.20.10 #76355
Conversation
Ah forgot to regenerate drone ... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This won't affect the release artifacts though. The only way to do that is change the default Go version in grafana-build or pass the --go-version argument when calling the "package" command
Yes, that's also incoming. Just doing too much in parallel right now :) |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
* [v10.1.x] Chore: Upgrade Go to 1.20.10 * Rebuild .drone.yml (cherry picked from commit 4287686)
* [v10.1.x] Chore: Upgrade Go to 1.20.10 * Rebuild .drone.yml (cherry picked from commit 4287686)
* [v10.1.x] Chore: Upgrade Go to 1.20.10 * Rebuild .drone.yml (cherry picked from commit 4287686)
* [v10.1.x] Chore: Upgrade Go to 1.20.10 * Rebuild .drone.yml
Note that this is not a backport from main as main currently looks totally different and so we take v10.1.x as starting point for the rest of the backport