-
-
Notifications
You must be signed in to change notification settings - Fork 384
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: update to golang 1.19 #2026
Conversation
Codecov ReportBase: 36.45% // Head: 36.43% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #2026 +/- ##
==========================================
- Coverage 36.45% 36.43% -0.02%
==========================================
Files 228 228
Lines 19316 19316
==========================================
- Hits 7041 7038 -3
- Misses 11442 11444 +2
- Partials 833 834 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
28edac6
to
94256b7
Compare
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)What kind of change does this PR introduce?
It updates the golang language version used in the source files. The version is bumped from go 1.17 to go 1.19.
The change will provide the latest security patches and bug fixes in the standard library and it will allow developers to write code with modern syntax.
In this regard the main language feature brought in are generics, that enable writing of simpler and more concise interfaces in addition to the possibility to use such interfaces from third party modules.
See golang release notes for more details.
It also update
go.sum
files after runninggo mod tidy
What is the current behavior?
What is the new behavior?
Does this PR introduce a breaking change, and is titled accordingly?
Not on the interface behaviours, but it's worth mentioning that go 1.19 is now required for compilation.
Other information