Increment go.mod Go version to 1.22 #735
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With the approaching release, the go version within go.mod can be incremented to a current Go version.
There were some small changes regarding the go.mod's go semantic since Go version 1.21, mainly enforcing compilation with a compatible version1. As other modules' go.mod files are now also being included, there are additional entries in go.sum.
@lippserd: As we talked about bumping the number to 1.21 or 1.22, I thought going up directly to the latest release would be more future proof. However, if you would prefer 1.21, I would alter this PR.
Footnotes
https://go.dev/doc/modules/gomod-ref#go ↩