deps: bump go version to 1.24#8509
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #8509 +/- ##
==========================================
- Coverage 82.40% 81.74% -0.66%
==========================================
Files 414 413 -1
Lines 40531 40525 -6
==========================================
- Hits 33399 33129 -270
- Misses 5770 6008 +238
- Partials 1362 1388 +26 🚀 New features to boost your workflow:
|
|
Hi @kevinGC, can you also bump the Go versions used for CI tests similar to this change? |
It's generally useful to have new-and-improved Go. One specific useful feature is `b.Loop()`, which makes benchmarking easier.
|
Thanks for the review. Done. |
arjan-bal
left a comment
There was a problem hiding this comment.
LGTM, adding a second reviewer.
Just FYI, gRPC Go supports the two most recent major versions of Golang, which aligns with Go's support policy. I'm not sure if it's a coincidence that this PR came just 6 hours after Go 1.25 was released. :)
|
personally I find it annoying when a library forces a bump without taking advantage of any actual feature - ie a just bumping while things compile fine with older (ps not to say that that when building end product one shouldn't indeed use the most recent stable patch (1.24.8 as of this writing) but forcing cascading bumps into dependencies is annoying (and golang.org/x is a prime culprit there but it would be nice the rest of the ecosystem doesn't imitate bad things)) |
It's generally useful to have new-and-improved Go. One specific useful feature is
b.Loop(), which makes benchmarking easier.Encountered while working on #8510, as I was using
b.Loop()in my benchmarks.RELEASE NOTES: