Update dependencies#705
Merged
Merged
Conversation
The go.mod directive now needs to define the build number. This was not the case in previous version of Go. Upgrade to Go 1.22 in both go.mod and in the CI flow to accomodate for this change. This does mean that future versions of model require Go 1.22+
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Starting with Go 1.21, the Go directive in
go.modneeds to define the build number.This was not the case in previous version of Go (and was an error to do so). Upgrade
to Go 1.22 in both go.mod and in the CI flow to accommodate for this change. This
does mean that future versions of model require Go 1.22+